Upgrade k8s package verison (#5358)

* upgrade k8s package version

Signed-off-by: hongzhouzi <hongzhouzi@kubesphere.io>

* Script upgrade and code formatting.

Signed-off-by: hongzhouzi <hongzhouzi@kubesphere.io>

Signed-off-by: hongzhouzi <hongzhouzi@kubesphere.io>

vendor/k8s.io/api/discovery/v1/generated.proto

@@ -27,7 +27,7 @@ import "k8s.io/apimachinery/pkg/runtime/generated.proto";
 import "k8s.io/apimachinery/pkg/runtime/schema/generated.proto";
 
 // Package-wide variables from generator "generated".
-option go_package = "v1";
+option go_package = "k8s.io/api/discovery/v1";
 
 // Endpoint represents a single logical "backend" implementing a service.
 message Endpoint {
@@ -35,7 +35,8 @@ message Endpoint {
   // according to the corresponding EndpointSlice addressType field. Consumers
   // must handle different types of addresses in the context of their own
   // capabilities. This must contain at least one address but no more than
-  // 100.
+  // 100. These are all assumed to be fungible and clients may choose to only
+  // use the first element. Refer to: https://issue.k8s.io/106267
   // +listType=set
   repeated string addresses = 1;
 
@@ -65,8 +66,7 @@ message Endpoint {
   map<string, string> deprecatedTopology = 5;
 
   // nodeName represents the name of the Node hosting this endpoint. This can
-  // be used to determine endpoints local to a Node. This field can be enabled
-  // with the EndpointSliceNodeName feature gate.
+  // be used to determine endpoints local to a Node.
   // +optional
   optional string nodeName = 6;
 
@@ -115,6 +115,7 @@ message EndpointHints {
 }
 
 // EndpointPort represents a Port used by an EndpointSlice
+// +structType=atomic
 message EndpointPort {
   // The name of this port. All ports in an EndpointSlice must have a unique
   // name. If the EndpointSlice is dervied from a Kubernetes service, this
@@ -139,7 +140,7 @@ message EndpointPort {
   // The application protocol for this port.
   // This field follows standard Kubernetes label syntax.
   // Un-prefixed names are reserved for IANA standard service names (as per
-  // RFC-6335 and http://www.iana.org/assignments/service-names).
+  // RFC-6335 and https://www.iana.org/assignments/service-names).
   // Non-standard protocols should use prefixed names such as
   // mycompany.com/my-custom-protocol.
   // +optional