Conformance results for v1.26/TencentCloud

[wqq578]

Pre-submission checklist:

Please check each of these after submitting your pull request:

• If this is a new entry, have you submitted a signed participation form?
• Did you include the product/project logo in SVG, EPS or AI format?
• Does your logo clearly state the name of the product/project and follow the other logo guidelines?
• If your product/project is open source, did you include the repo_url?
• Did you copy and paste the installation and configuration instructions into the README.md file in addition to linking to them?

For a full list of requirements, please refer to these sections of the docs: Contents of the PR, and Requirements.

[kubernetes-conformance-bot]

8 of 15 requirements have passed. Please review the following:

• [FAIL] the submission seems to contain files of multiple Kubernetes release versions or products. Each Kubernetes release version and products should be submitted in a separate PRs
  • there should be a single set of products in the submission. We found 2 product submissions: v1.24/tencentcloud, v1.26/tencentcloud
• [FAIL] the title of the submission does not seem to contain a Kubernetes release version that matches the release version in the submitted files
  • the Kubernetes release version in the title (v1.26) and folder structure (v1.24) don't match
• [FAIL] it appears that the PRODUCT.yaml file does not contain all the required fields (https://github.com/cncf/k8s-conformance/blob/master/instructions.md#productyaml)
  • missing or empty field 'contact_email_address' in file 'PRODUCT.yaml'
• [FAIL] it seems the e2e.log does not contain the Kubernetes release version that match the submission title
  • the Kubernetes release version in file 'e2e.log' (v1.26.0) doesn't match the same version in the folder structure (v1.24)
• [FAIL] it appears that some tests are missing from the product submission
  • the following test(s) are missing:
    • [sig-instrumentation] Events should ensure that an event can be fetched, patched, deleted, and listed [Conformance]
    • [sig-network] Services should have session affinity timeout work for NodePort service [LinuxOnly] [Conformance]
    • [sig-network] Services should have session affinity timeout work for service with type clusterIP [LinuxOnly] [Conformance]
    • [sig-node] Kubelet when scheduling a busybox Pod with hostAliases should write entries to /etc/hosts [LinuxOnly] [NodeConformance] [Conformance]
• [FAIL] it appears that some tests failed in the product submission
  • there appears to be 4 tests missing:
    • [sig-instrumentation] Events should ensure that an event can be fetched, patched, deleted, and listed [Conformance]
    • [sig-network] Services should have session affinity timeout work for NodePort service [LinuxOnly] [Conformance]
    • [sig-network] Services should have session affinity timeout work for service with type clusterIP [LinuxOnly] [Conformance]
    • [sig-node] Kubelet when scheduling a busybox Pod with hostAliases should write entries to /etc/hosts [LinuxOnly] [NodeConformance] [Conformance]
• [FAIL] it appears that there is a mismatch of tests in junit_01.xml and e2e.log
  • there appears to be 4 tests missing:
    • [sig-instrumentation] Events should ensure that an event can be fetched, patched, deleted, and listed [Conformance]
    • [sig-network] Services should have session affinity timeout work for NodePort service [LinuxOnly] [Conformance]
    • [sig-network] Services should have session affinity timeout work for service with type clusterIP [LinuxOnly] [Conformance]
    • [sig-node] Kubelet when scheduling a busybox Pod with hostAliases should write entries to /etc/hosts [LinuxOnly] [NodeConformance] [Conformance]

for a full list of requirements, please refer to these sections of the docs: content of the PR, and requirements.

[kubernetes-conformance-bot]

All requirements (15) have passed for the submission!

[taylorwaggoner]

@wqq578 please make sure to sign off on this PR correctly, per the DCO check above. Thanks!

[taylorwaggoner]

You are now Certified Kubernetes