Uodate README table with WIP backends separated from complete ones

[jayunit100]

So far IPTables, IPVS are pretty stable passing 100s of the CI tests etc, with only a few bugs ( < 5 tests ).

But others (eBPF and NFT) arent as well tested.

A good first issue for someone would be to test all backends and write up into the README which ones we consider experimental

• on ipv6
• on ipv4
• what % tests fail (sig-net/conformance)

/good-first-issue

[k8s-ci-robot]

@jayunit100:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

So far IPTables, IPVS are pretty stable passing 100s of the CI tests etc, with only a few bugs ( < 5 tests ).

But others (eBPF and NFT) arent as well tested.

A good first issue for someone would be to test all backends and write up into the README which ones we consider experimental

• on ipv6
• on ipv4
• what % tests fail (sig-net/conformance)

/good-first-issue

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.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[emabota]

Hi @jayunit100,
I think that I can also try this one. Please let me know how or from where to begin. Thanks
/assign

[jayunit100]

• e2e test suite fails but job succeeds #400 looking at antoinios PR, there are 2 failuires in iptables that are non-trivial.
• What other failures are non trivial ?

 ./test_e2e.sh -i ipv4 -b iptables
 ./test_e2e.sh -i ipv6 -b iptables
 ./test_e2e.sh -i ipv4 -b ipvs
  ./test_e2e.sh -i ipv6 -b ebpf

docs/TEST_REPORT_12_7_2022.md

Backend: Iptables
Stack: ipv4
Results:
   Mostly passing 215 of the tests.
   The two failures appear to be related to nodeports / clusterIPs.  
   Filed issues to look into it: xxx yyy

Backend: IPVS 
Stack:...

[emabota]

After running ./test_e2e.sh -i ipv4 -b iptables the cluster is created and the output of kubectl cluster-info is:

$ kubectl cluster-info 
Kubernetes control plane is running at https://127.0.0.1:36355
CoreDNS is running at https://127.0.0.1:36355/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

But the control plane is actually running on http and not https. Consequently, it seems that many tests are Failing as they attempt to connect through https.

Am I missing something or this is a bug?