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

Switch istio ztunnel and cni images to proper registry1 source #1225

Open
mjnagel opened this issue Jan 24, 2025 · 1 comment · May be fixed by #1256
Open

Switch istio ztunnel and cni images to proper registry1 source #1225

mjnagel opened this issue Jan 24, 2025 · 1 comment · May be fixed by #1256
Assignees

Comments

@mjnagel
Copy link
Contributor

mjnagel commented Jan 24, 2025

Describe what should be investigated or refactored

In #1175 we introduced the optional ztunnel and cni components. At the time the registry1 images were non-functional so we added placeholders for the upstream images from dockerhub.

The original issues have now been closed so we should re-test the latest published versions and see if they work now. If they are functioning, we will need to swap them in. If they are non-functional then we should report any additional issues upstream in repo1.

Links to any relevant code

Images to be swapped in (note that we should use the tetrate images as these ones are/will be FIPS compliant):

registry1.dso.mil/ironbank/tetrate/istio/install-cni:1.24.2-tetratefips-v0
registry1.dso.mil/ironbank/tetrate/istio/ztunnel:1.24.2-tetratefips0

Additional context

https://repo1.dso.mil/dsop/tetrate/istio/1.24/ztunnel/-/issues/9

https://repo1.dso.mil/dsop/tetrate/istio/1.24/install-cni/-/issues/11

@mjnagel mjnagel self-assigned this Feb 3, 2025
mjnagel added a commit that referenced this issue Feb 3, 2025
## Description

Switches the registry1 flavored ztunnel image to the registry1 source.
Note that there is still an issue with the install-cni image that has
been reported upstream.

Also updated docs to note additional modules from the upstream docs -
https://istio.io/latest/docs/ops/deployment/platform-requirements/

## Related Issue

Related to #1225

## Type of change

- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [x] Other (security config, docs update, etc)

## Steps to Validate

N/A, could test deploy with the istio-ambient component enabled.

## Checklist before merging

- [x] Test, docs, adr added or updated as needed
- [x] [Contributor
Guide](https://github.com/defenseunicorns/uds-template-capability/blob/main/CONTRIBUTING.md)
followed
@mjnagel mjnagel linked a pull request Feb 4, 2025 that will close this issue
5 tasks
@mjnagel
Copy link
Contributor Author

mjnagel commented Feb 4, 2025

Ztunnel switched to registry1. Still working through some issues with the install-cni image, reported upstream but having a hard time getting it reproduced on the maintainer's side.

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 a pull request may close this issue.

1 participant