chore (kubernetes-model-generator) : Upgrade Fabric8 Kubernetes Model to Kubernetes v1.26.0 (#4655)

[rohanKanojia]

Description

Fix #4655 #4804

• Upgrade Fabric8 Kubernetes Model to Kubernetes v1.26.0
• Add Kubernetes 1.26.0 to Kubernetes E2E tests matrix
  • Add Kubernetes 1.26.0 to Kubernetes E2E tests matrix
  • Set Driver=docker and container-runtime=containerd in minikube GitHub
    action in order to run Kubernetes 1.26
• Update Kubernetes Model GatewayApi to v0.6.0 (The attribute of ‘responseHeaderModifier’ is not in class named io.fabric8.kubernetes.api.model.gatewayapi.v1beta1.HTTPRouteFilter #4804)
  • gateway.networking.k8s.io/v1alpha2 ReferencePolicy struct removed from kubernetes-model-gatewayapi in favor of
    ReferenceGrant
  • Updating Kubernetes Model Gateway breaks build for cert-manager extension. It also needs to be updated to the latest version which uses latest sigs.k8s.io/gateway-api dependency

New Resources

• Add admissionregistration.k8s.io/v1alpha1
  • ValidatingAdmissionPolicy
  • ValidatingAdmissionPolicyBinding
• Add flowcontrol.apiserver.k8s.io/v1beta3
  • FlowSchema
  • PriorityLevelConfiguration
• Add authentication.k8s.io/v1alpha1
  • SelfSubjectReview
• Add new module kubernetes-model-resource for
  resource.k8s.io/v1alpha1 apiGroup.
  • ResourceClaimTemplate
  • ResourceClaim
  • ResourceClass
  • PodScheduling

Other Changes

• New field ordinals of type StatefulSetOrdinals added to StatefulSetSpec
• PersistentVolumeClaimSpec's dataSourceRef changed from TypedLocalObjectReference -> TypedObjectReference
• New list fields resourceClaims and schedulingGates of type PodResourceClaim and PodSchedulingGate added to PodSpec
• New list field claims of type ResourceClaim added to ResourceRequirements
• IngressStatus's loadBalancer field type changed from LoadBalancerStatus -> IngressLoadBalancerStatus
• New field unhealthyPodEvictionPolicy added to PodDisruptionBudgetSpec

Signed-off-by: Rohan Kumar rohaan@redhat.com

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change
• Chore (non-breaking change which doesn't affect codebase;
  test, version modification, documentation, etc.)

Checklist

• Code contributed by me aligns with current project license: Apache 2.0
• I Added CHANGELOG entry regarding this change
• I have implemented unit tests to cover my changes
• I have added/updated the javadocs and other documentation accordingly
• No new bugs, code smells, etc. in SonarCloud report
• I tested my code in Kubernetes
• I tested my code in OpenShift

[manusa]

Comparing with OpenAPI generation results.
The following new APIs are available:

• admissionregistration.k8s.io/v1alpha1
• authentication.k8s.io/v1alpha1
• flowcontrol.apiserver.k8s.io/v1beta3
• resource.k8s.io/v1alpha1

I see you added DSL for FlowControl and AdmissionRegistration, but can't see the other two.

[shawkins]

LGTM

[sonarcloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

35.0% Coverage
0.0% Duplication