Added Netris and description

[ixodie]

Added description of Netris integration with k8s and included links to solution overview and k8s chart (github).

Content is additive, no conflicts.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign tengqm after the PR has been reviewed.
You can assign the PR to them by writing /assign @tengqm in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• content/en/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

✔️ Deploy Preview for kubernetes-io-main-staging ready!

🔨 Explore the source changes: d45d610

🔍 Inspect the deploy log: https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/611a78e480ec2c00078646a5

😎 Browse the preview: https://deploy-preview-29021--kubernetes-io-main-staging.netlify.app

[sftim]

Reviewers / approvers: please verify that this content is allowed by the content guide.

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: login-issues@jira.linuxfoundation.org

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[ixodie]

("I signed it")

[tengqm]

We don't use words like "simple", "modern" ...

"native integration", "with which" ... are confusing too.

[tengqm]

L4LB is a not a term widely used in the k8s community.
Use relative path (i.e. /docs/tasks/...) rather than full path.

[ixodie]

/check-cla

[ixodie]

/check-cla

[tengqm]

/lgtm

[ixodie]

@thockin I think you are the last reviewer for this one. Thanks!

[ixodie]

@thockin Waiting on your approval for this to get merged. Thanks!

[sftim]

/hold

@tengqm - let's make sure we're clear that this is definitely allowed by the content guide. What was your thinking for determining that it is?

[ixodie]

My $.02

This supporting software solution offers integration with multiple CNCF/LFN projects including FRR/DPDK/k8s/haproxy. These configurations are built to properly route and load balance traffic to the ingress based on a deployment.

There will be a free offering of this product announced at Kubecon 2021 in a month.

Netris is a supporting member of CNCF and LFN.

There are multiple entries in this list which have literally ZERO integration with k8s.

This entry offers both CRD and Operator model integrations, as well as integration with Calico for the recommended performance mode design.

[sftim]

There are multiple entries in this list which have literally ZERO integration with k8s.

All these entries should be capable of taking a Kubernetes cluster that is missing networking, and implementing the Kubernetes network model (eg: by providing a compatible CNI plugin).

We'll accept PRs to remove any entry that doesn't provide Kubernetes-compatible networking. See #20232

[ixodie]

There are multiple entries in this list which have literally ZERO integration with k8s.

All these entries should be capable of taking a Kubernetes cluster that is missing networking, and implementing the Kubernetes network model (eg: by providing a compatible CNI plugin).

We'll accept PRs to remove any entry that doesn't provide Kubernetes-compatible networking. See #20232

The "eg" part of your reply is what is confusing. All of these vendors provide creative ways of enabling network functionality either in a CNI or plugin, or via the host networking, or via the actual network itself.

If you want to draw the line at only allowing CNIs, then this would mean that the GCE entry should be completely removed, as this does not have a plugin/CNI. In fact this solution requires setting a kernel option to bridge onto the physical network. This entry seems completely orthogonal to a virtualized/containerized system like k8s.

Can you clarify what sort of cluster networking services should be admitted to this page? CNIs obviously, but what else?

[tengqm]

@sftim

let's make sure we're clear that this is definitely allowed by the content guide. What was your thinking for determining that it is?

This Netris thing looks like a (extended) CNI to me, which is an something one must install in order for making the kubernetes cluster work. According to our previous discussion on 3rd party contents, this one should be okay. By the way, I don't know the technology well. If you have a different opinion, just leave your comments here.

[ixodie]

@sftim

let's make sure we're clear that this is definitely allowed by the content guide. What was your thinking for determining that it is?

This Netris thing looks like a (extended) CNI to me, which is an something one must install in order for making the kubernetes cluster work. According to our previous discussion on 3rd party contents, this one should be okay. By the way, I don't know the technology well. If you have a different opinion, just leave your comments here.

No it is absolutely not a CNI. Bare metal and NIC subinterface integration only.

[tengqm]

@ixodie Thank you for the clarification. According to our content guide, we don't publish things like this. Please consider closing this PR.
/lgtm cancel

[reylejano]

If Netris does not implement the Kubernetes network model then I agree that Netris should not be added to the /concepts/cluster-administration/networking page according to "What's Allowed" in the Kubernetes Content Guide:

Kubernetes docs allow content for third-party projects only when:

• Content documents software in the Kubernetes project
• Content documents software that's out of project but necessary for Kubernetes to function
• Content is canonical on kubernetes.io, or links to canonical content elsewhere

[sftim]

With the previous reviews in mind:
/close

[k8s-ci-robot]

@sftim: Closed this PR.

In response to this:

With the previous reviews in mind:
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.