fixing issue #6 update the name of the secret in webhook.yaml #17
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.
fixing issue #6 Update the name of the secret in webhook.yaml so that it is aligned with the one in the deployment
The issue stated:
In helm/oci-native-ingress-controller/templates/webhook.yaml line 20 the name of the secret is hardcoded (oci-native-ingress-controller-tls), and this secret is referenced in helm/oci-native-ingress-controller/templates/deployment.yaml line 47, but this time the name of the secret is derived using a helm template function
Fixing the issue by:
replacing hardcode secret name in the webhook.yaml on line 20 with helm temple function.