-
Notifications
You must be signed in to change notification settings - Fork 45
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
chart: template and store Dex backend config in a ConfigMap #2274
chart: template and store Dex backend config in a ConfigMap #2274
Conversation
Hello ebaneck,My role is to assist you with the merge of this Status report is not available. |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option
|
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list:
|
ef71f77
to
137291a
Compare
History mismatchMerge commit #7ccf27e27b18b113debc54da198af8042d1ce300 on the integration branch It is likely due to a rebase of the branch Please use the |
137291a
to
93edf19
Compare
@@ -188,7 +212,7 @@ spec: | |||
template: | |||
metadata: | |||
annotations: | |||
checksum/config: 278f2b27e9441887e4070365aa3df2ccf668da0025ebf565605555c2b7b16042 | |||
checksum/config: 82272216f0373dd6510af9cea925a8642900f1fe7400d2cbcf4ef54e59ac7d9c |
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.
We're changing this when needed, right?
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 thought this checksum hashes are generated each time we render the charts? Don't we need to use the new values generated?
Also, when are we required to change it ?
9a7937c
to
9216a2b
Compare
fcd0065
to
c66ee29
Compare
Initially, we do not deploy and manage Dex service configurations using configmaps. This commit adds generic configmaps with service related configurations such that the end user can configure Dex settings directly by editing the related configmaps
We need to magically handle the subsititution of jinja looking urls to yaml.
This commit adds and templates the Dex service charts to directly consume configuration values from a ConfigMap
This chart is rendered using the following commmand: ./charts/render.py dex --namespace metalk8s-auth charts/dex.yaml --service-config dex metalk8s-dex-config charts/dex/ > salt/metalk8s/addons/dex/deployed/chart.sls Closes: #2261
c66ee29
to
d58300f
Compare
/reset |
Reset completeI have successfully deleted this pull request's integration branches. |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option
|
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list:
The following reviewers are expecting changes from the author, or must review again: |
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.
LGTM
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list:
|
/approve |
In the queueThe changeset has received all authorizations and has been added to the The changeset will be merged in:
The following branches will NOT be impacted:
There is no action required on your side. You will be notified here once IMPORTANT Please do not attempt to modify this pull request.
If you need this pull request to be removed from the queue, please contact a The following options are set: approve |
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue None. Goodbye ebaneck. |
Component:
'salt', 'kubernetes', 'chart'
Context:
See #2261
Summary:
Acceptance criteria:
Closes: #2261