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

Multus CNI updates for OCP 4.6 #71

Merged

Conversation

dougbtv
Copy link
Member

@dougbtv dougbtv commented Jul 22, 2020

Notably, this includes updates to vendored packages.

ICucos and others added 30 commits March 16, 2020 13:19
… 1.16 +. To be able to start cluster with version 1.16 i used rapid channel "gcloud beta container clusters create cluster --zone europe-west1-b --num-nodes=1 --machine-type=n1-standard-8 --image-type ubuntu --enable-network-policy --release-channel=rapid --enable-autorepair"
… pre 1.16. To be able to start cluster with version 1.15 i used "gcloud container clusters create cl-name --zone europe-west1-b --num-nodes=2 --machine-type=n1-standard-8 --image-type ubuntu --enable-network-policy --cluster-version=1.15.9-gke.24". !!!!important to start the cluster with --enable-network-policy that will enable CNI in kublet
Signed-off-by: Ted Yu <yuzhihong@gmail.com>
To troubleshooting #481, adds error message for further analysis.
Skip docker push action if REPOSITORY_PASS is not set
This fix removes redundant error messages and try to simplify
if the error comes from delegating CNI plugins.
Daemonset for Google Kubernetes Engine for kubernetes cluster version…
This change introduces gopkg.in to allow everyone to use multus
code as library. Currently multus-cni uses version 'v3', hence
it hits go modules limitation, as #504 describes.

This change fix #504 with gopkg.in.
This change adds retry to wait a bit if kubernetes client
returns service unavailable.

This fixes #492
Change the error handling for kubernetes client
This fix changes network status name to net-attach-def name with
namespace, to compliant with k8s npwg's multi-net-spec.
Fix network status name/namespace to compliant with multi-net-spec
When using debug level the log files tends to fill up quickly.
Add support for log rotation using lumberjack, simple and easy to use
log rotation module.

Signed-off-by: Shahar Klein <sklein@nvidia.com>
This change will enable builds to be performed with the option of
passing the -mod flag to 'go build'. This can be done by optionally
setting the MODMODE environment variable prior to building.

For example, toggling the -mod setting for the build can be
accomplished as follows:

```
$ MODMODE=vendor ./build
```

Signed-off-by: Ryan Tidwell <rtidwell@suse.com>
- Add `infinibandGUID` CNI runtime config
- Add `infiniband-guid` Network attachment attribute
- Reflect infiniband guid request in Delegate network config
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

23 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 91c7526 into openshift:master Jul 25, 2020
@smarterclayton
Copy link

How did this merge with the network name break? It seems like this should have failed to merge?

@smarterclayton
Copy link

This appears to be kubernetes/kubernetes#58711, which was fixed in 3.11 in openshift/origin@a6e1db6 but has not been deployed to api.ci. We either need to update the node or stop running pods on that.

@dougbtv
Copy link
Member Author

dougbtv commented Jul 27, 2020

@smarterclayton thanks for the heads up -- I might need a little more info.

How did this merge with the network name break? It seems like this should have failed to merge?

I'm unsure where this test may be, so I can't answer how. I did look at your reference of openshift/origin@a6e1db6 and I was specifically looking for any mention of using the networks-status annotation, specifically the changes made in this upstream PR https://github.com/intel/multus-cni/pull/515/files (which looks the closest to the description of "with the network name break") from this particular change set. However, I failed to find a reference -- I may be looking at the wrong thing.

To continue along that line, regarding https://github.com/intel/multus-cni/pull/515/files -- what this changes specifically the contents of an annotation on pods as processed by Multus, an annotation titled: k8s.v1.cni.cncf.io/networks-status (which is defined by the NPWG spec in section 5) this contains a JSON field, titled "name", which used to refer to the name of a network attachment definition. This change makes it so instead of referring to the name of a network attachment definition, it refers to the name and namespace of the network attachment definition, e.g. if you have a net-attach-def named bar in a namespace called foo the results of the name field of this JSON object will be foo/bar (whereas previously it was just bar).

In the meanwhile, @s1061123 is putting in a PR which reverts this change to k8s.v1.cni.cncf.io/networks-status as a stop-gap here, in case CI is broken elsewhere. @s1061123 also noted that he saw an inconsistency in CI (my notes suffered here, but, I think it was depending on a bot re-run? unsure. it was alarming enough to make us consider the revert).

@s1061123
Copy link
Contributor

@smarterclayton @dougbtv Filed revert PR as #72 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet