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

Spike: Determine what happens when a Multus network attachment definition gets changed #196

Closed
eak13 opened this issue Jul 14, 2021 · 4 comments
Closed

Spike: Determine what happens when a Multus network attachment definition gets changed #196

eak13 opened this issue Jul 14, 2021 · 4 comments
Assignees
@digambar15
Labels
Day2 Relates to day 2 operations (brownfield upgrades, etc.) enhancement New feature or request priority/medium Default priority for items size m 2-5 days [moderate complexity, generic code, or enhancement to existing feature]]
Milestone
v2.1

Comments

@eak13
Copy link

eak13 commented Jul 14, 2021 •
edited
Loading

Problem description (if applicable)
Multus provides the ability to connect multiple CNIs to one Kubernetes cluster. Once Multus has been deployed in a network-cloud type (dependent on #20), we want to understand what the impacts of changing the network attachment definitions.

https://github.com/k8snetworkplumbingwg/multus-cni/blob/master/README.md

Proposed Change
In a running cluster with Multus deployed, with at least 2 NADs defined:

  • Perform a configuration change to one of the NADs
  • Perform configuration changes to both NADs at the same time

Report back on :

  • Impacts to the interface with the changed NAD. Are there any restart implications?
  • Validate changing one NAD doesn't impact the other NAD defined by Multus
  • Any other change considerations
@eak13 eak13 added enhancement New feature or request triage Day2 Relates to day 2 operations (brownfield upgrades, etc.) labels Jul 14, 2021
@eak13 eak13 added this to the Future milestone Jul 14, 2021
@jezogwza jezogwza added the priority/medium Default priority for items label Jul 14, 2021
@jezogwza jezogwza modified the milestones: Future, v2.2 Jul 14, 2021
@jezogwza jezogwza removed the triage label Jul 14, 2021
@digambar15
Copy link
Contributor

@ak3216 Please assign me.

@eak13 eak13 added the size m 2-5 days [moderate complexity, generic code, or enhancement to existing feature]] label Jul 26, 2021
@digambar15
Copy link
Contributor

Design proposal is presented in DEsign meeting and it is also accepted. Can we close this issue as I already started working on developing the feature.

@digambar15
Copy link
Contributor

Can we close this issue as I already started the development work ?

@eak13 eak13 closed this as completed Sep 17, 2021
@eak13
Copy link
Author

eak13 commented Sep 17, 2021

Closing per above

@eak13 eak13 modified the milestones: v2.2, v2.1 Nov 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@digambar15 digambar15

Labels
Day2 Relates to day 2 operations (brownfield upgrades, etc.) enhancement New feature or request priority/medium Default priority for items size m 2-5 days [moderate complexity, generic code, or enhancement to existing feature]]
Projects
None yet
Milestone
v2.1
Development

No branches or pull requests
3 participants
@digambar15 @eak13 @jezogwza