Skip to content
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

enable using personalized pull-secret #82

Conversation

Gregory-Pereira
Copy link
Contributor

/cc @lance
/cc @tommyd450

@tommyd450
Copy link
Contributor

lgtm

Copy link
Collaborator

@sallyom sallyom left a comment

Choose a reason for hiding this comment

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

I'm confused as to when the non-default pull secret will be required - I'm ok with adding this but eventually we'll want this script to evolve into a proper installer/CRD with fields for OIDC provider, BYO root certs, etc.

@Gregory-Pereira
Copy link
Contributor Author

Just to clarify, Sally, By non-default pull-secret do you mean the TAS specific one that people can download from the console dot? If so that is used for metrics in the write home job to we can track usage and installations. +1 on all the other eventual requirements, I think that stuff is important, but I think it might be a good idea to implement those when we move to the operator.

@Gregory-Pereira
Copy link
Contributor Author

Moving this to nightlyMetrics pr (#81) because it fits better there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants