Update upstream specifications to their latest version

Author: sebhoss

crd-catalog/3scale/apicast-operator/apps.3scale.net/v1alpha1/apicasts.yaml

@@ -130,6 +130,8 @@ spec:
                   properties:
                     host:
                       type: "string"
+                    ingressClassName:
+                      type: "string"
                     tls:
                       items:
                         description: "IngressTLS describes the transport layer security associated with an ingress."

crd-catalog/Kuadrant/dns-operator/kuadrant.io/v1alpha1/dnsrecords.yaml

@@ -99,7 +99,7 @@ spec:
                           type: "string"
                         type: "array"
                     type: "object"
-                  minItems: 1
+                  minItems: 0
                   type: "array"
                 healthCheck:
                   description: "HealthCheckSpec configures health checks in the DNS provider.\nBy default this health check will be applied to each unique DNS A Record for\nthe listeners assigned to the target gateway"

crd-catalog/VictoriaMetrics/operator/operator.victoriametrics.com/v1beta1/vmagents.yaml

@@ -1449,7 +1449,7 @@ spec:
                   type: "object"
                   x-kubernetes-map-type: "atomic"
                 remoteWrite:
-                  description: "RemoteWrite list of victoria metrics /some other remote write system\nfor vm it must looks like: http://victoria-metrics-single:8429/api/v1/write\nor for cluster different url\nhttps://docs.victoriametrics.com/victoriametrics/vmagent/#splitting-data-streams-among-multiple-systems"
+                  description: "RemoteWrite list of victoria metrics /some other remote write system\nfor vm it must looks like: http://victoria-metrics-single:8428/api/v1/write\nor for cluster different url\nhttps://docs.victoriametrics.com/victoriametrics/vmagent/#splitting-data-streams-among-multiple-systems"
                   items:
                     description: "VMAgentRemoteWriteSpec defines the remote storage configuration for VmAgent"
                     properties:

crd-catalog/VictoriaMetrics/operator/operator.victoriametrics.com/v1beta1/vmusers.yaml

@@ -205,7 +205,7 @@ spec:
                           type: "string"
                         type: "array"
                       static:
-                        description: "Static - user defined url for traffic forward,\nfor instance http://vmsingle:8429"
+                        description: "Static - user defined url for traffic forward,\nfor instance http://vmsingle:8428"
                         properties:
                           url:
                             description: "URL http url for given staticRef."

crd-catalog/aerospike/aerospike-kubernetes-operator/asdb.aerospike.com/v1/aerospikeclusters.yaml

@@ -896,6 +896,22 @@ spec:
                   required:
                     - "enabled"
                   type: "object"
+                namespaceManagement:
+                  description: "NamespaceManagement defines the list of namespaces that Argo CD is allowed to manage."
+                  items:
+                    description: "NamespaceManagement defines the namespace management settings"
+                    properties:
+                      allowManagedBy:
+                        description: "Whether the namespace can be managed by ArgoCD"
+                        type: "boolean"
+                      name:
+                        description: "Name of the namespace or pattern to be managed"
+                        type: "string"
+                    required:
+                      - "allowManagedBy"
+                      - "name"
+                    type: "object"
+                  type: "array"
                 nodePlacement:
                   description: "NodePlacement defines NodeSelectors and Taints for Argo CD workloads"
                   properties:

crd-catalog/argoproj-labs/argocd-operator/argoproj.io/v1alpha1/argocds.yaml

@@ -81,9 +81,9 @@ spec:
                   description: "The name of the add-on. The name must match one of the names returned by\nDescribeAddonVersions."
                   type: "string"
                 podIdentityAssociations:
-                  description: "An array of Pod Identity Assocations to be created. Each EKS Pod Identity\nassociation maps a Kubernetes service account to an IAM Role.\n\nFor more information, see Attach an IAM Role to an Amazon EKS add-on using\nPod Identity (https://docs.aws.amazon.com/eks/latest/userguide/add-ons-iam.html)\nin the Amazon EKS User Guide."
+                  description: "An array of EKS Pod Identity associations to be created. Each association\nmaps a Kubernetes service account to an IAM role.\n\nFor more information, see Attach an IAM Role to an Amazon EKS add-on using\nEKS Pod Identity (https://docs.aws.amazon.com/eks/latest/userguide/add-ons-iam.html)\nin the Amazon EKS User Guide."
                   items:
-                    description: "A type of Pod Identity Association owned by an Amazon EKS Add-on.\n\nEach EKS Pod Identity Association maps a role to a service account in a namespace\nin the cluster.\n\nFor more information, see Attach an IAM Role to an Amazon EKS add-on using\nPod Identity (https://docs.aws.amazon.com/eks/latest/userguide/add-ons-iam.html)\nin the Amazon EKS User Guide."
+                    description: "A type of EKS Pod Identity association owned by an Amazon EKS add-on.\n\nEach association maps a role to a service account in a namespace in the cluster.\n\nFor more information, see Attach an IAM Role to an Amazon EKS add-on using\nEKS Pod Identity (https://docs.aws.amazon.com/eks/latest/userguide/add-ons-iam.html)\nin the Amazon EKS User Guide."
                     properties:
                       roleARN:
                         type: "string"

crd-catalog/argoproj-labs/argocd-operator/argoproj.io/v1beta1/argocds.yaml

@@ -59,7 +59,7 @@ spec:
                       type: "boolean"
                   type: "object"
                 bootstrapSelfManagedAddons:
-                  description: "If you set this value to False when creating a cluster, the default networking\nadd-ons will not be installed.\n\nThe default networking addons include vpc-cni, coredns, and kube-proxy.\n\nUse this option when you plan to install third-party alternative add-ons\nor self-manage the default networking add-ons."
+                  description: "If you set this value to False when creating a cluster, the default networking\nadd-ons will not be installed.\n\nThe default networking add-ons include vpc-cni, coredns, and kube-proxy.\n\nUse this option when you plan to install third-party alternative add-ons\nor self-manage the default networking add-ons."
                   type: "boolean"
                 clientRequestToken:
                   description: "A unique, case-sensitive identifier that you provide to ensurethe idempotency\nof the request."
@@ -155,11 +155,11 @@ spec:
                       type: "array"
                   type: "object"
                 remoteNetworkConfig:
-                  description: "The configuration in the cluster for EKS Hybrid Nodes. You can't change or\nupdate this configuration after the cluster is created."
+                  description: "The configuration in the cluster for EKS Hybrid Nodes. You can add, change,\nor remove this configuration after the cluster is created."
                   properties:
                     remoteNodeNetworks:
                       items:
-                        description: "A network CIDR that can contain hybrid nodes.\n\nThese CIDR blocks define the expected IP address range of the hybrid nodes\nthat join the cluster. These blocks are typically determined by your network\nadministrator.\n\nEnter one or more IPv4 CIDR blocks in decimal dotted-quad notation (for example,\n10.2.0.0/16).\n\nIt must satisfy the following requirements:\n\n   * Each block must be within an IPv4 RFC-1918 network range. Minimum allowed\n   size is /24, maximum allowed size is /8. Publicly-routable addresses aren't\n   supported.\n\n   * Each block cannot overlap with the range of the VPC CIDR blocks for\n   your EKS resources, or the block of the Kubernetes service IP range.\n\n   * Each block must have a route to the VPC that uses the VPC CIDR blocks,\n   not public IPs or Elastic IPs. There are many options including Transit\n   Gateway, Site-to-Site VPN, or Direct Connect.\n\n   * Each host must allow outbound connection to the EKS cluster control\n   plane on TCP ports 443 and 10250.\n\n   * Each host must allow inbound connection from the EKS cluster control\n   plane on TCP port 10250 for logs, exec and port-forward operations.\n\n   * Each host must allow TCP and UDP network connectivity to and from other\n   hosts that are running CoreDNS on UDP port 53 for service and pod DNS\n   names."
+                        description: "A network CIDR that can contain hybrid nodes.\n\nThese CIDR blocks define the expected IP address range of the hybrid nodes\nthat join the cluster. These blocks are typically determined by your network\nadministrator.\n\nEnter one or more IPv4 CIDR blocks in decimal dotted-quad notation (for example,\n10.2.0.0/16).\n\nIt must satisfy the following requirements:\n\n   * Each block must be within an IPv4 RFC-1918 network range. Minimum allowed\n   size is /32, maximum allowed size is /8. Publicly-routable addresses aren't\n   supported.\n\n   * Each block cannot overlap with the range of the VPC CIDR blocks for\n   your EKS resources, or the block of the Kubernetes service IP range.\n\n   * Each block must have a route to the VPC that uses the VPC CIDR blocks,\n   not public IPs or Elastic IPs. There are many options including Transit\n   Gateway, Site-to-Site VPN, or Direct Connect.\n\n   * Each host must allow outbound connection to the EKS cluster control\n   plane on TCP ports 443 and 10250.\n\n   * Each host must allow inbound connection from the EKS cluster control\n   plane on TCP port 10250 for logs, exec and port-forward operations.\n\n   * Each host must allow TCP and UDP network connectivity to and from other\n   hosts that are running CoreDNS on UDP port 53 for service and pod DNS\n   names."
                         properties:
                           cidrs:
                             items:
@@ -169,7 +169,7 @@ spec:
                       type: "array"
                     remotePodNetworks:
                       items:
-                        description: "A network CIDR that can contain pods that run Kubernetes webhooks on hybrid\nnodes.\n\nThese CIDR blocks are determined by configuring your Container Network Interface\n(CNI) plugin. We recommend the Calico CNI or Cilium CNI. Note that the Amazon\nVPC CNI plugin for Kubernetes isn't available for on-premises and edge locations.\n\nEnter one or more IPv4 CIDR blocks in decimal dotted-quad notation (for example,\n10.2.0.0/16).\n\nIt must satisfy the following requirements:\n\n   * Each block must be within an IPv4 RFC-1918 network range. Minimum allowed\n   size is /24, maximum allowed size is /8. Publicly-routable addresses aren't\n   supported.\n\n   * Each block cannot overlap with the range of the VPC CIDR blocks for\n   your EKS resources, or the block of the Kubernetes service IP range."
+                        description: "A network CIDR that can contain pods that run Kubernetes webhooks on hybrid\nnodes.\n\nThese CIDR blocks are determined by configuring your Container Network Interface\n(CNI) plugin. We recommend the Calico CNI or Cilium CNI. Note that the Amazon\nVPC CNI plugin for Kubernetes isn't available for on-premises and edge locations.\n\nEnter one or more IPv4 CIDR blocks in decimal dotted-quad notation (for example,\n10.2.0.0/16).\n\nIt must satisfy the following requirements:\n\n   * Each block must be within an IPv4 RFC-1918 network range. Minimum allowed\n   size is /32, maximum allowed size is /8. Publicly-routable addresses aren't\n   supported.\n\n   * Each block cannot overlap with the range of the VPC CIDR blocks for\n   your EKS resources, or the block of the Kubernetes service IP range."
                         properties:
                           cidrs:
                             items:

crd-catalog/aws-controllers-k8s/eks-controller/eks.services.k8s.aws/v1alpha1/addons.yaml

@@ -113,7 +113,7 @@ spec:
                   description: "The Kubernetes labels to apply to the nodes in the node group when they are\ncreated."
                   type: "object"
                 launchTemplate:
-                  description: "An object representing a node group's launch template specification. When\nusing this object, don't directly specify instanceTypes, diskSize, or remoteAccess.\nMake sure that the launch template meets the requirements in launchTemplateSpecification.\nAlso refer to Customizing managed nodes with launch templates (https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html)\nin the Amazon EKS User Guide."
+                  description: "An object representing a node group's launch template specification. When\nusing this object, don't directly specify instanceTypes, diskSize, or remoteAccess.\nYou cannot later specify a different launch template ID or name than what\nwas used to create the node group.\n\nMake sure that the launch template meets the requirements in launchTemplateSpecification.\nAlso refer to Customizing managed nodes with launch templates (https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html)\nin the Amazon EKS User Guide."
                   properties:
                     id:
                       type: "string"