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

Get namespace for updating objects from build artifact #951

Merged
merged 1 commit into from
Sep 4, 2018

Conversation

priyawadhwa
Copy link
Contributor

When deploying with helm to a non-default namespace, we were seeing the warning "error adding label
to runtime object". This was because accessor.GetNamespace() always
returned an empty string rather than the specified namespace. It seems
the original object returned by helm doesn't have the namespace field specified.

To fix this problem, we can access the namespace from the build artifact
instead of the accessor.

Should fix #899

When deploying with helm to a non-default namespace, we were seeing the warning "error adding label
to runtime object". This was because accessor.GetNamespace() always
returned an empty string rather than the specified namespace. It seems
the original object doesn't have the namespace field specified.

To fix this problem, we can access the namespace from the build artifact
instead of the accessor.

Should fix GoogleContainerTools#899
@priyawadhwa priyawadhwa changed the title Get namespace for updating objects via res.Namespacea Get namespace for updating objects from build artifact Sep 4, 2018
@codecov-io
Copy link

Codecov Report

Merging #951 into master will not change coverage.
The diff coverage is 0%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #951   +/-   ##
=======================================
  Coverage   43.28%   43.28%           
=======================================
  Files          63       63           
  Lines        2629     2629           
=======================================
  Hits         1138     1138           
  Misses       1372     1372           
  Partials      119      119
Impacted Files Coverage Δ
pkg/skaffold/deploy/labels.go 0% <0%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3cfdf89...e6421c0. Read the comment docs.

@priyawadhwa
Copy link
Contributor Author

The kaniko test on kokoro is failing because it's unable to push images (has been happening all morning since GCR is experiencing outages)

I'll try running it again.

@priyawadhwa priyawadhwa added the kokoro:run runs the kokoro jobs on a PR label Sep 4, 2018
@kokoro-team kokoro-team removed the kokoro:run runs the kokoro jobs on a PR label Sep 4, 2018
@priyawadhwa priyawadhwa merged commit 1354cb4 into GoogleContainerTools:master Sep 4, 2018
@priyawadhwa priyawadhwa deleted the helm branch September 4, 2018 22:31
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.

Skaffold fails to patch resources with deploy result labels using Helm deployer
4 participants