simplify operatorspec to match what we ended up needing#285
simplify operatorspec to match what we ended up needing#285openshift-merge-robot merged 1 commit intoopenshift:masterfrom
Conversation
openshift-ci-robot
added
the
size/M
openshift-ci-robot
added
the
approved
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, derekwaynecarr The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
| type StaticPodOperatorSpec struct { | ||
| OperatorSpec `json:",inline"` | ||
|
|
||
| // forceRedeploymentReason can be used to force the redeployment of the kube-controller-manager by providing a unique string. |
There was a problem hiding this comment.
copy paste of kube-controller-manager
|
|
||
| // operandSpecs provide customization for functional units within the component | ||
| // +optional | ||
| OperandSpecs []OperandSpec `json:"operandSpecs,omitempty"` |
There was a problem hiding this comment.
I assume we simply do not want support for applying a patch on the operand's deployment/pod?
There was a problem hiding this comment.
I assume we simply do not want support for applying a patch on the operand's deployment/pod?
We don't today. We'll see what we need later
deads2k
force-pushed
the
operator-reality
branch
from
8dd984e to
a8cf1d7
Compare
|
Should delete Lines 24 to 28 in a8cf1d7 |
6 participants
We are able to simplify the operator spec based on what has actually been necessary.