-
Notifications
You must be signed in to change notification settings - Fork 46
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
feat: add cosi transformer for harbor and kubecost #1544
Conversation
Signed-off-by: Tarun Gupta Akirala <[email protected]>
Signed-off-by: Tarun Gupta Akirala <[email protected]>
Signed-off-by: Tarun Gupta Akirala <[email protected]>
10508f7
to
351652e
Compare
--from-literal=REGISTRY_STORAGE_S3_SECRETKEY=$(kubectl get secret {{ .credentialsSecretName }} -n {{ $ns }} -o jsonpath="{.data.BucketInfo}" | base64 --decode | jq -r '.spec.secretS3.accessSecretKey') \ | ||
--dry-run=client -o yaml | kubectl apply -f - | ||
# Create a configmap with the name of the secret from above. | ||
kubectl create configmap {{ $cmName }} -n {{ $ns }} \ |
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.
kubectl create configmap {{ $cmName }} -n {{ $ns }} \ | |
kubectl create configmap {{ $cmName }} -n kommander \ |
The overrides CM needs to be created in the ns of the harbor HelmRelease
- in the kommander
ns.
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.
Discussed offline and since this doesn't work on attached clusters, decided to add a new namespace param (mesosphere/kommander-applications@bd212e4)
Co-authored-by: Martin Hrabovcin <[email protected]>
Signed-off-by: Tarun Gupta Akirala <[email protected]>
Signed-off-by: Tarun Gupta Akirala <[email protected]>
Co-authored-by: Martin Hrabovcin <[email protected]>
…d-by: Martin Hrabovcin <[email protected]>
What type of PR is this?
Add a cosi secret transformer for harbor
What this PR does/ why we need it:
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Checklist