-
Notifications
You must be signed in to change notification settings - Fork 251
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
[BUG] crc and snc don't use the same routes-controller image #3502
Comments
I suspect because of this inconsistency crc pulls the routes-controller image from quay at cluster creation instead of reusing the cached one. If the cached image is still the latest one, it's not very important, but if the cached one is no longer also the latest, this is more problematic |
inconsistencies like this can lead to hard to track issues. we can't assume these are both pointing to 'latest'. It would be better to use a tag that is identical on both ends. |
In case of openshift preset we should use the image tag as Edit: looks like we don't need this image for podman preset and we might put this logic to the snc side and in crc side just create the deployment/pod. |
This PR adds deployment resource for route controller which use correct image tag, what we cached. Once the bundle is created using this PR, we will also need to make change on crc side. The resource file is located in `/opt` dir same as `kubeconfig` file. - crc-org/crc#3502
This PR adds deployment resource for route controller which use correct image tag, what we cached. Once the bundle is created using this PR, we will also need to make change on crc side. The resource file is located in `/opt` dir same as `kubeconfig` file. - crc-org/crc#3502
This PR adds deployment resource for route controller which use correct image tag, what we cached. Once the bundle is created using this PR, we will also need to make change on crc side. The resource file is located in `/opt` dir same as `kubeconfig` file. - crc-org/crc#3502
This PR adds deployment resource for route controller which use correct image tag, what we cached. Once the bundle is created using this PR, we will also need to make change on crc side. The resource file is located in `/opt/crc` dir. - crc-org/crc#3502
This PR adds deployment resource for route controller which use correct image tag, what we cached. Once the bundle is created using this PR, we will also need to make change on crc side. The resource file is located in `/opt/crc` dir. - crc-org/crc#3502
This PR adds deployment resource for route controller which use correct image tag, what we cached. Once the bundle is created using this PR, we will also need to make change on crc side. The resource file is located in `/opt/crc` dir. Also if we take this in it will not going to have any effect on created bundle until we implement the logic on crc side and it will be just a unused extra file in the bundle. - crc-org/crc#3502
This PR adds deployment resource for route controller which use correct image tag, what we cached. Once the bundle is created using this PR, we will also need to make change on crc side. The resource file is located in `/opt/crc` dir. Also if we take this in it will not going to have any effect on created bundle until we implement the logic on crc side and it will be just a unused extra file in the bundle. - crc-org/crc#3502
This PR adds deployment resource for route controller which use correct image tag, what we cached. Once the bundle is created using this PR, we will also need to make change on crc side. The resource file is located in `/opt/crc` dir. Also if we take this in it will not going to have any effect on created bundle until we implement the logic on crc side and it will be just a unused extra file in the bundle. - crc-org/crc#3502
This PR adds deployment resource for route controller which use correct image tag, what we cached. Once the bundle is created using this PR, we will also need to make change on crc side. The resource file is located in `/opt/crc` dir. Also if we take this in it will not going to have any effect on created bundle until we implement the logic on crc side and it will be just a unused extra file in the bundle. - crc-org/crc#3502
This is fixed by crc-org/snc@fe6a6d2 /close |
@praveenkumar: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
snc uses
quay.io/crcont/routes-controller:${image_tag}
https://github.com/crc-org/snc/blob/4ada0a93e0e3de2b0fbd328ef43096c7563a7ed9/createdisk.sh#L79-L80
crc uses
quay.io/crcont/routes-controller:latest
crc/pkg/crc/machine/start.go
Lines 835 to 844 in 3291661
Not sure which one should be changed, the easiest would be to tag
quay.io/crcont/routes-controller:${image_tag}
aslatest
when pulling it insnc
, but I'm not surecrictl
supports setting tags.The text was updated successfully, but these errors were encountered: