Skip to content
This repository was archived by the owner on Jun 3, 2025. It is now read-only.

upgrade go container registry to latest master#1146

Merged
tejal29 merged 2 commits intoGoogleContainerTools:masterfrom
tejal29:up_ggcr
Mar 24, 2020
Merged

upgrade go container registry to latest master#1146
tejal29 merged 2 commits intoGoogleContainerTools:masterfrom
tejal29:up_ggcr

Conversation

@tejal29
Copy link
Copy Markdown
Contributor

@tejal29 tejal29 commented Mar 18, 2020

Fixes #1144

Ran

go get -u github.com/google/go-containerregistry
go mod tidy

@googlebot googlebot added the cla: yes CLA signed by all commit authors label Mar 18, 2020
@tejal29 tejal29 requested a review from mattmoor March 18, 2020 22:02
@tejal29
Copy link
Copy Markdown
Contributor Author

tejal29 commented Mar 18, 2020

@mattmoor Feel free to build the kaniko executor image with the instructions below to proceed with your testing.

REGISTRY=<you registry> make images

@mattmoor
Copy link
Copy Markdown
Contributor

Things look kinda broken. Should I wait?

@tejal29
Copy link
Copy Markdown
Contributor Author

tejal29 commented Mar 18, 2020

Things look kinda broken. Should I wait?

yep sorry, i missed to add the vendor/modules.txt changes.

@tejal29
Copy link
Copy Markdown
Contributor Author

tejal29 commented Mar 18, 2020

@samos123
Copy link
Copy Markdown
Contributor

it shouldn't have run K8s tests in that test run, for some reason the TestK8s wasn't excluded correctly. I'm looking into it more.

@samos123
Copy link
Copy Markdown
Contributor

It's weird, this PR worked fine and also ran K8s tests separately: https://travis-ci.org/github/GoogleContainerTools/kaniko/builds/664580845?utm_source=github_status&utm_medium=notification. So not sure what's different here and why -list=Test is not returning the correct output...

@samos123
Copy link
Copy Markdown
Contributor

I restarted that specific job and it now succeeded, for some reason the make integration-test-misc script ran all tests instead of only the misc tests and I still don't know why.

@mattmoor
Copy link
Copy Markdown
Contributor

@tejal29 if this is ready for me to try out, I will do that tomorrow?

@mattmoor
Copy link
Copy Markdown
Contributor

@tejal29 tl;dr success!

I built this image and copied it to docker.io/mattmoor/kaniko:tejal and ran it via the Tekton task on EKS with the following setup:

# Cluster must have oidc enabled:
eksctl utils associate-iam-oidc-provider --name knative-aws --approve

# Create service account with:
eksctl create iamserviceaccount \
  --name builder \
  --namespace default \
  --cluster knative-aws \
  --attach-policy-arn arn:aws:iam::aws:policy/AmazonEC2ContainerRegistryPowerUser \
  --approve

I then ran the Tekton TaskRun as the service account builder that the above creates, and it worked great!

@tejal29 tejal29 merged commit d5d20b6 into GoogleContainerTools:master Mar 24, 2020
@tejal29
Copy link
Copy Markdown
Contributor Author

tejal29 commented Mar 24, 2020

great Thanks @mattmoor. I will probably release this in v0.20.0 and let you know when its released.

@mattmoor
Copy link
Copy Markdown
Contributor

Perfect, thanks!

@mattmoor
Copy link
Copy Markdown
Contributor

Maybe worth a PR to the tekton Catalog when that comes out? tektoncd/catalog#235

@Vlatombe Vlatombe mentioned this pull request Mar 24, 2020
4 tasks
@tejal29 tejal29 deleted the up_ggcr branch April 26, 2021 16:43
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

cla: yes CLA signed by all commit authors

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Pick up latest GGCR

4 participants