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

Define phase to apply Calico network policies #119

Closed
eak13 opened this issue Mar 30, 2021 · 3 comments
Closed

Define phase to apply Calico network policies #119

eak13 opened this issue Mar 30, 2021 · 3 comments
Assignees
Labels
2-Manifests Relates to manifest/document set related issues enhancement New feature or request priority/critical Items critical to be implemented, usually by the next release size m 2-5 days [moderate complexity, generic code, or enhancement to existing feature]] type: airship-core Used to identify a function will be associated with the airship-core type.
Projects
Milestone

Comments

@eak13
Copy link

eak13 commented Mar 30, 2021

Define a custom phase for the airship-core type to implement the Calico network policies defined in #43. It should use the generic container leveraging calicoctl being defined in airshipit/airshipctl#494.

@eak13 eak13 added enhancement New feature or request triage labels Mar 30, 2021
@eak13 eak13 added this to To do in Airship 2.0 via automation Mar 30, 2021
@eak13 eak13 added this to the v2.1 milestone Mar 30, 2021
@eak13 eak13 added the type: airship-core Used to identify a function will be associated with the airship-core type. label Mar 30, 2021
@ratnopamc
Copy link
Contributor

Please assign this issue to me. Thanks.

@eak13
Copy link
Author

eak13 commented Mar 30, 2021

@eratnch all yours

@lb4368 lb4368 added size m 2-5 days [moderate complexity, generic code, or enhancement to existing feature]] 2-Manifests Relates to manifest/document set related issues labels Apr 7, 2021
@ratnopamc
Copy link
Contributor

PS https://review.opendev.org/c/airship/treasuremap/+/786905 is ready for review.
Thanks!

@eak13 eak13 added the priority/critical Items critical to be implemented, usually by the next release label Apr 26, 2021
Airship 2.0 automation moved this from To do to Done May 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2-Manifests Relates to manifest/document set related issues enhancement New feature or request priority/critical Items critical to be implemented, usually by the next release size m 2-5 days [moderate complexity, generic code, or enhancement to existing feature]] type: airship-core Used to identify a function will be associated with the airship-core type.
Projects
Airship 2.0
  
Done
Development

No branches or pull requests

3 participants