-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
controllers: fix available crd #257
controllers: fix available crd #257
Conversation
Testing:
|
|
babfd4d
to
ae28c53
Compare
ae28c53
to
401b166
Compare
The PR does the following 1. gcr.io/distroless/static:nonroot does not allow us to run bash scripts, since with available crd we are capturing the exit via a bash script, moving to use registry.access.redhat.com/ubi9/ubi-minimal as the base 2. remove caching only storageCluster crd 3. fix panic while logging Signed-off-by: Rewant Soni <[email protected]>
401b166
to
a580d05
Compare
Testing -
|
Yes, I checked it for any other exitcode/panic it restarts the container. For the restart exit code it restarts the manager |
&extv1.CustomResourceDefinition{}: { | ||
// only cache storagecluster crd | ||
Field: storageclustersSelector, | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I understand this removal, was a corresponding watch added on this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From what I recall, this is used when we deploy CSI and it will be removed in 4.18. Do we need a watch on this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Until we remove that we need this, is it effecting your feature?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, if we specify the CRD to cache here, the operator will only be caching that particular CRD and we cannot have multiple resource names in the field Selector.
If needed, I can add StorageCluster CRD to how we are watching the CRD (with avail CRD feature). WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ack, that can be separate PR, when we get RC I'll be cleaning up lot of code, waiting for that.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: leelavg, rewantsoni The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
7d67155
into
red-hat-storage:main
The PR does the following
bash scripts, since with available crd we are capturing the exit
via a bash script, moving to use
registry.access.redhat.com/ubi9/ubi-minimal as the base