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

ci: embed prod policy settings on release #164

Merged
merged 3 commits into from
Feb 22, 2024
Merged

Conversation

burgerdev
Copy link
Contributor

This commit blesses the Microsoft fork of the Kata Containers policy and settings.

Why not ours?

  • Any divergence from upstream configs risks security relevant divergence and would need continuous justification.
  • We can contribute missing policy features upstream, if needed.

Why not kata-containers/kata-containers?

  • We assume that the Microsoft fork is customized to the AKS environment that we're targeting, and we want to stay compatible with that.
  • The genpolicy tool and its config are not compatible across minor versions (e.g., a policy generated from Kata head today is not accepted by the Kata Agent available in the AKS preview today).

@malt3
Copy link
Contributor

malt3 commented Feb 15, 2024

I think that's a good idea.
Just a conceptual question: shouldn't we also use this policy during our e2e tests? Otherwise we might build features that are not compatible with the msft policies (and not notice until we release a new version).

@burgerdev
Copy link
Contributor Author

I think that's a good idea. Just a conceptual question: shouldn't we also use this policy during our e2e tests? Otherwise we might build features that are not compatible with the msft policies (and not notice until we release a new version).

Excellent suggestion, let me add that to the proposal.

Base automatically changed from burgerdev/policy to main February 19, 2024 13:20
@burgerdev burgerdev force-pushed the burgerdev/release-policy branch from c75eda4 to 54e3bfd Compare February 20, 2024 11:28
@burgerdev burgerdev marked this pull request as ready for review February 20, 2024 13:49
@burgerdev burgerdev requested a review from malt3 February 20, 2024 13:51
justfile Outdated Show resolved Hide resolved
@burgerdev burgerdev force-pushed the burgerdev/release-policy branch 3 times, most recently from d995ef8 to 2771f54 Compare February 21, 2024 15:25
This commit blesses the Microsoft fork of the Kata Containers policy and
settings.

Why not ours?

* Any divergence from upstream configs risks security relevant
  divergence and would need continuous justification.
* We can contribute missing policy features upstream, if needed.

Why not kata-containers/kata-containers?

* We assume that the Microsoft fork is customized to the AKS environment
  that we're targeting, and we want to stay compatible with that.
* The genpolicy tool and its config are not compatible across minor
  versions (e.g., a policy generated from Kata head today is not
  accepted by the Kata Agent available in the AKS preview today).
Introduces a new parameter for some just targets that allows overriding
the nix rule used to build the cli.

The dev variant stays the default, while the release variant is used for
e2e testing.
@burgerdev burgerdev force-pushed the burgerdev/release-policy branch from 2771f54 to 49dc9af Compare February 21, 2024 17:27
@burgerdev burgerdev merged commit c620ebd into main Feb 22, 2024
5 checks passed
@burgerdev burgerdev deleted the burgerdev/release-policy branch February 22, 2024 07:46
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 this pull request may close these issues.

3 participants