]
Jeff Mesnil commented on WFWIP-193:
-----------------------------------
The recommendation is to not touch internal objects.
The Operator "owns" the underlying Kubernetes resources based on the
WildFlyServer spec and may modify/delete them without notice to update its cluster state.
Is updating Kubernetes objects created by Operator supported?
-------------------------------------------------------------
Key: WFWIP-193
URL:
https://issues.jboss.org/browse/WFWIP-193
Project: WildFly WIP
Issue Type: Bug
Components: OpenShift
Reporter: Martin Choma
Assignee: Jeff Mesnil
Priority: Blocker
Technically it is possible to update Kubernetes objects which were created by Operator,
e.g. StatefulSet, Pods, ...
- Operator has its limitation compared to non-Operator approach (ports, volume mounts,
deployment strategy, ...) So user may be tempted to tweak internal objects manually
- But some values of internal objects are automatically synced with Operator (env,..). So
even changed they are overwritten by original operator values after a while.
What will be our general recommendation to users:
- Dont touch internal objects?
- We will document what can't be touched?
- We will document what can be touched?