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

Test CKF 1.8 in airgapped environment #889

Open
ca-scribner opened this issue May 7, 2024 · 3 comments
Open

Test CKF 1.8 in airgapped environment #889

ca-scribner opened this issue May 7, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@ca-scribner
Copy link
Contributor

Context

We need to test CKF 1.8 in an airgapped environment after:

What needs to get done

.

Definition of Done

  1. CKF 1.8 is shown to work in airgapped
@ca-scribner ca-scribner added the enhancement New feature or request label May 7, 2024
Copy link

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5643.

This message was autogenerated

@NohaIhab
Copy link
Contributor

NohaIhab commented May 23, 2024

During test CKF in airgapped, it has been discovered that some charms' images were not in the local registry, and are not in the retagged-images.txt. Turns out the new charms in CKF 1.8 do not have the get-images.sh in their repos that is necessary for get-all-images.sh to add the images to the list and pull them. To fix that, I sent PRs for these charms to have the script:
canonical/mlmd-operator#83
canonical/pvcviewer-operator#37
canonical/envoy-operator#96

In addition, the mysql-k8s-operator charm was missing the github dependency repo and branch fields in our 1.8 bundle yaml, these are necessary for the get-all-images.sh script to get the mysql image. Sent a fix in #902.

@NohaIhab
Copy link
Contributor

To run the tests, we are using the script in bundle-kubeflow repo to setup the airgapped env. The script did not work out of the box with uk8s 1.25 and juju 3.1, in addition to a bug in py-docker. To address these blockers, I sent #904. See all the details in the PR description.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants