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

cni: network.cni job updates should replace allocs #23764

Merged
merged 1 commit into from
Aug 7, 2024

Conversation

gulducat
Copy link
Member

@gulducat gulducat commented Aug 7, 2024

We missed this tiny bit when enabling CNI_ARGS-in-the-jobspec in #23538

A change to the network{cni{}} block means that the user wants the network config to change, and that only happens during initial alloc setup, so we need to replace the alloc(s) to get fresh network(s) to reconfigure from scratch.

e.g. a job plan diff like this

+/- Task Group: "g" (1 in-place update)
  + Network {
    + CNIConfig {
      + a: "ayy"
      }

should instead be

+/- Task Group: "g" (1 create/destroy update)
  + Network {
    + CNIConfig {
      + a: "ayy"
      }

@gulducat gulducat added theme/jobspec theme/cni backport/1.8.x backport to 1.8.x release line labels Aug 7, 2024
@gulducat gulducat requested review from philrenaud and martisah August 7, 2024 16:26
a change to the network{cni{}} block means that
the user wants the network config to change,
and that only happens during initial alloc setup,
so we need to replace the alloc(s) to get
fresh network(s) to reconfigure from scratch.

e.g. a job plan diff like this

```
+/- Task Group: "g" (1 in-place update)
  + Network {
    + CNIConfig {
      + a: "ayy"
      }
```

should instead be

```
+/- Task Group: "g" (1 create/destroy update)
  + Network {
    + CNIConfig {
      + a: "ayy"
      }
```
@gulducat gulducat merged commit d131c41 into main Aug 7, 2024
19 checks passed
@gulducat gulducat deleted the cni-block-update-destructive branch August 7, 2024 17:13
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
backport/1.8.x backport to 1.8.x release line theme/cni theme/jobspec
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants