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

fix(local): fix local profiles for kubernetes v2 deployments #923

Merged
merged 1 commit into from
Apr 24, 2018

Conversation

danielpeach
Copy link
Contributor

No description provided.

Copy link
Member

@lwander lwander left a comment

Choose a reason for hiding this comment

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

Does this have to be done for each deployment type?

@danielpeach
Copy link
Contributor Author

Yes, will go back and add in.

@danielpeach danielpeach merged commit 8fbd98b into spinnaker:master Apr 24, 2018
@danielpeach danielpeach deleted the local-k8s-v2 branch April 24, 2018 12:15
@ghost
Copy link

ghost commented May 14, 2018

Is there any documentation that can walk me through the steps needed to disable Halyard from checking the list of published versions, the BOM and going to external gcr repo during when i run hal deploy.

Please your guidance will be highly appreciated

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.

2 participants