Skip to content

Conversation

bergerhoffer
Copy link
Contributor

@bergerhoffer bergerhoffer commented Sep 2, 2021

@bergerhoffer bergerhoffer added this to the Future Release milestone Sep 2, 2021
@openshift-ci openshift-ci bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Sep 2, 2021
@netlify
Copy link

netlify bot commented Sep 2, 2021

✔️ Deploy Preview for osdocs ready!

🔨 Explore the source changes: 44cacb7

🔍 Inspect the deploy log: https://app.netlify.com/sites/osdocs/deploys/616706f96aa137000836685e

😎 Browse the preview: https://deploy-preview-36040--osdocs.netlify.app

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@stlaz Prior to this, we said that you had to set up the LDAP IDP. If you look at our docs on it [1] the names are ldap-secret for the secret, and ca-config-map. Any thoughts on if we should use those names, or are they too generic?

[1] https://docs.openshift.com/container-platform/4.8/authentication/identity_providers/configuring-ldap-identity-provider.html#identity-provider-creating-ldap-secret_configuring-ldap-identity-provider

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@stlaz Did you have any thoughts on this question here?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you can refer to the secret used in the IdP configuration, specific names are probably not necessary in the description.

@bergerhoffer bergerhoffer force-pushed the OSDOCS-1856 branch 2 times, most recently from b788450 to 2742912 Compare September 14, 2021 23:51
@bergerhoffer
Copy link
Contributor Author

Note to self: change batch/v1 to batch/v1beta1 for the 4.6 and 4.7 backports

@bergerhoffer bergerhoffer force-pushed the OSDOCS-1856 branch 2 times, most recently from 96fd7f0 to 5399203 Compare September 16, 2021 03:37
@bobfuru bobfuru self-assigned this Sep 30, 2021
@bobfuru bobfuru added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-needed Signifies that the peer review team needs to review this PR labels Sep 30, 2021
Copy link
Contributor

@bobfuru bobfuru left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple of very minor comments but this LGTM!

@bergerhoffer
Copy link
Contributor Author

Note to self again: change batch/v1 to batch/v1beta1 for the 4.6 and 4.7 backports.

Copy link

@yaoli-redhat yaoli-redhat Oct 8, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is the ca filed required when insecure is false? Will 'insecure is true' be supported?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should the url be ldaps rather than ldap?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd prefer this being ldaps:// actually, but ldap:// should still work

@bergerhoffer
Copy link
Contributor Author

@stlaz Can you take a look at @yaoli-redhat's comments? I don't know the answer to them.

@bergerhoffer
Copy link
Contributor Author

@yaoli-redhat Per @stlaz's answer and discussion in slack, I updated ldap:// to ldaps://. And he said that insecure:false was the default, so it should be fine to keep, so I left that alone.

Can you take another look with that update and let me know how this looks? Thanks!

@yaoli-redhat
Copy link

@bergerhoffer thanks for the update and lgtm.

@bergerhoffer
Copy link
Contributor Author

Thanks @yaoli-redhat!

@bergerhoffer
Copy link
Contributor Author

/cherrypick enterprise-4.9

@openshift-cherrypick-robot

@bergerhoffer: once the present PR merges, I will cherry-pick it on top of enterprise-4.9 in a new PR and assign it to you.

In response to this:

/cherrypick enterprise-4.9

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@bergerhoffer
Copy link
Contributor Author

/cherrypick enterprise-4.8

@openshift-cherrypick-robot

@bergerhoffer: once the present PR merges, I will cherry-pick it on top of enterprise-4.8 in a new PR and assign it to you.

In response to this:

/cherrypick enterprise-4.8

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@bergerhoffer
Copy link
Contributor Author

4.6 and 4.7 backports to be done manually so that I can change batch/v1 to batch/v1beta1 for these versions.

@openshift-cherrypick-robot

@bergerhoffer: new pull request created: #37520

In response to this:

/cherrypick enterprise-4.9

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-cherrypick-robot

@bergerhoffer: new pull request created: #37521

In response to this:

/cherrypick enterprise-4.8

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.6 branch/enterprise-4.7 branch/enterprise-4.8 branch/enterprise-4.9 peer-review-done Signifies that the peer review team has reviewed this PR size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants