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.

Sign up for GitHub

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

Jump to bottom

Nightly testing of integration points (Azure) #1615

Closed
Tracked by #2512
Racer159 opened this issue Apr 18, 2023 · 2 comments
Closed
Tracked by #2512

Nightly testing of integration points (Azure) #1615

Racer159 opened this issue Apr 18, 2023 · 2 comments
Labels
ga Issues tracking toward Zarf 1.0 tech-debt 💳 Debt that the team has charged and needs to repay

Comments

@Racer159
Copy link
Contributor

Racer159 commented Apr 18, 2023 •
edited
Loading

Describe what should be investigated or refactored

Zarf integrates with many external services and each of these has its unique *ilities that are likely to change over time. We should be checking against the following:

  • A wide range of kubernetes cluster versions and distros
  • A wide range of git repositories (for flux deployments)
  • A wide range of image registries (for deployments and zarf package publishing/deploying)

Links to any relevant code

https://github.com/defenseunicorns/zarf/tree/main/.github/workflows

Additional context

This is the Azure version of this issue and focuses on AKS and ACR for deployment and ACR for package publish (see #1407)
@Racer159 Racer159 added the tech-debt 💳 Debt that the team has charged and needs to repay label Apr 18, 2023
@Racer159 Racer159 added this to the GA milestone Apr 26, 2023
@Racer159 Racer159 added the ga Issues tracking toward Zarf 1.0 label May 4, 2023
@Racer159 Racer159 removed this from the GA milestone May 4, 2023
@Noxsios
Copy link
Contributor

Noxsios commented May 5, 2023

Since GHCR is hosted on Azure (pretty sure), Github/GHCR tests should also happen in this PR.

First one to test: #1677, pulling unauthenticated from GHCR

@schristoff-du schristoff-du mentioned this issue May 16, 2024
Closed
17 tasks
@schristoff-du
Copy link
Contributor

At this time, we aren't seeing enough issues with Azure to commit to creating & maintaining an Azure E2E test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ga Issues tracking toward Zarf 1.0 tech-debt 💳 Debt that the team has charged and needs to repay
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Racer159 @Noxsios @schristoff-du