fix : remove kube-rbac-proxy
sidecar metric proxy container from Operator deployment
#1437
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
As mentioned in #1352 and #1343 (comment) , using
kube-rbac-proxy
sidecar container is deprecated and is causing issues in configuring Operator resource/limits via Operator subscription.This PR removes this sidecar container and uses controller-runtime's inbuilt
WithAuthenticationAndAuthorization
. Now that we don't have a proxy, we can directly post metrics on 8443 and 9443 ports for devworkspace-controller-manager and devworkspace-webhook-server respectively.Signed-off-by: Rohan Kumar [email protected]
What issues does this PR fix or reference?
#1343
Is it tested? How?
After making changes I made sure operator is running and metrics are accessible on 8443 and 9443 ports.
NAMESPACE=devworkspace-controller
make docker
make install
PR Checklist
/test v8-devworkspace-operator-e2e, v8-che-happy-path
to trigger)v8-devworkspace-operator-e2e
: DevWorkspace e2e testv8-che-happy-path
: Happy path for verification integration with Che