diff --git a/operators/ack-ecs-controller/0.0.8/bundle.Dockerfile b/operators/ack-ecs-controller/0.0.8/bundle.Dockerfile new file mode 100644 index 00000000000..b5e1fa6ca70 --- /dev/null +++ b/operators/ack-ecs-controller/0.0.8/bundle.Dockerfile @@ -0,0 +1,21 @@ +FROM scratch + +# Core bundle labels. +LABEL operators.operatorframework.io.bundle.mediatype.v1=registry+v1 +LABEL operators.operatorframework.io.bundle.manifests.v1=manifests/ +LABEL operators.operatorframework.io.bundle.metadata.v1=metadata/ +LABEL operators.operatorframework.io.bundle.package.v1=ack-ecs-controller +LABEL operators.operatorframework.io.bundle.channels.v1=alpha +LABEL operators.operatorframework.io.bundle.channel.default.v1=alpha +LABEL operators.operatorframework.io.metrics.builder=operator-sdk-v1.28.0 +LABEL operators.operatorframework.io.metrics.mediatype.v1=metrics+v1 +LABEL operators.operatorframework.io.metrics.project_layout=unknown + +# Labels for testing. +LABEL operators.operatorframework.io.test.mediatype.v1=scorecard+v1 +LABEL operators.operatorframework.io.test.config.v1=tests/scorecard/ + +# Copy files to locations specified by labels. +COPY bundle/manifests /manifests/ +COPY bundle/metadata /metadata/ +COPY bundle/tests/scorecard /tests/scorecard/ diff --git a/operators/ack-ecs-controller/0.0.8/manifests/ack-ecs-controller.clusterserviceversion.yaml b/operators/ack-ecs-controller/0.0.8/manifests/ack-ecs-controller.clusterserviceversion.yaml new file mode 100644 index 00000000000..99a2cd78f79 --- /dev/null +++ b/operators/ack-ecs-controller/0.0.8/manifests/ack-ecs-controller.clusterserviceversion.yaml @@ -0,0 +1,369 @@ +apiVersion: operators.coreos.com/v1alpha1 +kind: ClusterServiceVersion +metadata: + annotations: + alm-examples: |- + [ + { + "apiVersion": "ecs.services.k8s.aws/v1alpha1", + "kind": "Service", + "metadata": { + "name": "example" + }, + "spec": {} + }, + { + "apiVersion": "ecs.services.k8s.aws/v1alpha1", + "kind": "Cluster", + "metadata": { + "name": "example" + }, + "spec": {} + }, + { + "apiVersion": "ecs.services.k8s.aws/v1alpha1", + "kind": "TaskDefinition", + "metadata": { + "name": "example" + }, + "spec": {} + } + ] + capabilities: Basic Install + categories: Cloud Provider + certified: "false" + containerImage: public.ecr.aws/aws-controllers-k8s/ecs-controller:0.0.8 + createdAt: "2024-08-06T21:20:27Z" + description: AWS ECS controller is a service controller for managing ECS resources + in Kubernetes + operatorframework.io/suggested-namespace: ack-system + operators.operatorframework.io/builder: operator-sdk-v1.28.0 + operators.operatorframework.io/project_layout: unknown + repository: https://github.com/aws-controllers-k8s + support: Community + labels: + operatorframework.io/arch.amd64: supported + operatorframework.io/arch.arm64: supported + operatorframework.io/os.linux: supported + name: ack-ecs-controller.v0.0.8 + namespace: placeholder +spec: + apiservicedefinitions: {} + customresourcedefinitions: + owned: + - description: Cluster represents the state of an AWS ecs Cluster resource. + displayName: Cluster + kind: Cluster + name: clusters.ecs.services.k8s.aws + version: v1alpha1 + - description: Service represents the state of an AWS ecs Service resource. + displayName: Service + kind: Service + name: services.ecs.services.k8s.aws + version: v1alpha1 + - description: TaskDefinition represents the state of an AWS ecs TaskDefinition + resource. + displayName: TaskDefinition + kind: TaskDefinition + name: taskdefinitions.ecs.services.k8s.aws + version: v1alpha1 + description: |- + Manage Amazon Elastic Container Service (ECS) resources in AWS from within your Kubernetes cluster. + + **About Amazon ECS** + + Amazon Elastic Container Service (Amazon ECS) is a fully managed container orchestration service that helps you easily deploy, manage, and scale containerized applications. As a fully managed service, Amazon ECS comes with AWS configuration and operational best practices built-in. It's integrated with both AWS and third-party tools, such as Amazon Elastic Container Registry and Docker. This integration makes it easier for teams to focus on building the applications, not the environment. You can run and scale your container workloads across AWS Regions in the cloud, and on-premises, without the complexity of managing a control plane. + + **About the AWS Controllers for Kubernetes** + + This controller is a component of the [AWS Controller for Kubernetes](https://github.com/aws/aws-controllers-k8s) project. + + **Pre-Installation Steps** + + Please follow the following link: [Red Hat OpenShift](https://aws-controllers-k8s.github.io/community/docs/user-docs/openshift/) + displayName: AWS Controllers for Kubernetes - Amazon ECS + icon: + - base64data: PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KPCEtLSBHZW5lcmF0b3I6IEFkb2JlIElsbHVzdHJhdG9yIDE5LjAuMSwgU1ZHIEV4cG9ydCBQbHVnLUluIC4gU1ZHIFZlcnNpb246IDYuMDAgQnVpbGQgMCkgIC0tPgo8c3ZnIHZlcnNpb249IjEuMSIgaWQ9IkxheWVyXzEiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgeG1sbnM6eGxpbms9Imh0dHA6Ly93d3cudzMub3JnLzE5OTkveGxpbmsiIHg9IjBweCIgeT0iMHB4IiB2aWV3Qm94PSIwIDAgMzA0IDE4MiIgc3R5bGU9ImVuYWJsZS1iYWNrZ3JvdW5kOm5ldyAwIDAgMzA0IDE4MjsiIHhtbDpzcGFjZT0icHJlc2VydmUiPgo8c3R5bGUgdHlwZT0idGV4dC9jc3MiPgoJLnN0MHtmaWxsOiMyNTJGM0U7fQoJLnN0MXtmaWxsLXJ1bGU6ZXZlbm9kZDtjbGlwLXJ1bGU6ZXZlbm9kZDtmaWxsOiNGRjk5MDA7fQo8L3N0eWxlPgo8Zz4KCTxwYXRoIGNsYXNzPSJzdDAiIGQ9Ik04Ni40LDY2LjRjMCwzLjcsMC40LDYuNywxLjEsOC45YzAuOCwyLjIsMS44LDQuNiwzLjIsNy4yYzAuNSwwLjgsMC43LDEuNiwwLjcsMi4zYzAsMS0wLjYsMi0xLjksM2wtNi4zLDQuMiAgIGMtMC45LDAuNi0xLjgsMC45LTIuNiwwLjljLTEsMC0yLTAuNS0zLTEuNEM3Ni4yLDkwLDc1LDg4LjQsNzQsODYuOGMtMS0xLjctMi0zLjYtMy4xLTUuOWMtNy44LDkuMi0xNy42LDEzLjgtMjkuNCwxMy44ICAgYy04LjQsMC0xNS4xLTIuNC0yMC03LjJjLTQuOS00LjgtNy40LTExLjItNy40LTE5LjJjMC04LjUsMy0xNS40LDkuMS0yMC42YzYuMS01LjIsMTQuMi03LjgsMjQuNS03LjhjMy40LDAsNi45LDAuMywxMC42LDAuOCAgIGMzLjcsMC41LDcuNSwxLjMsMTEuNSwyLjJ2LTcuM2MwLTcuNi0xLjYtMTIuOS00LjctMTZjLTMuMi0zLjEtOC42LTQuNi0xNi4zLTQuNmMtMy41LDAtNy4xLDAuNC0xMC44LDEuM2MtMy43LDAuOS03LjMsMi0xMC44LDMuNCAgIGMtMS42LDAuNy0yLjgsMS4xLTMuNSwxLjNjLTAuNywwLjItMS4yLDAuMy0xLjYsMC4zYy0xLjQsMC0yLjEtMS0yLjEtMy4xdi00LjljMC0xLjYsMC4yLTIuOCwwLjctMy41YzAuNS0wLjcsMS40LTEuNCwyLjgtMi4xICAgYzMuNS0xLjgsNy43LTMuMywxMi42LTQuNWM0LjktMS4zLDEwLjEtMS45LDE1LjYtMS45YzExLjksMCwyMC42LDIuNywyNi4yLDguMWM1LjUsNS40LDguMywxMy42LDguMywyNC42VjY2LjR6IE00NS44LDgxLjYgICBjMy4zLDAsNi43LTAuNiwxMC4zLTEuOGMzLjYtMS4yLDYuOC0zLjQsOS41LTYuNGMxLjYtMS45LDIuOC00LDMuNC02LjRjMC42LTIuNCwxLTUuMywxLTguN3YtNC4yYy0yLjktMC43LTYtMS4zLTkuMi0xLjcgICBjLTMuMi0wLjQtNi4zLTAuNi05LjQtMC42Yy02LjcsMC0xMS42LDEuMy0xNC45LDRjLTMuMywyLjctNC45LDYuNS00LjksMTEuNWMwLDQuNywxLjIsOC4yLDMuNywxMC42ICAgQzM3LjcsODAuNCw0MS4yLDgxLjYsNDUuOCw4MS42eiBNMTI2LjEsOTIuNGMtMS44LDAtMy0wLjMtMy44LTFjLTAuOC0wLjYtMS41LTItMi4xLTMuOUw5Ni43LDEwLjJjLTAuNi0yLTAuOS0zLjMtMC45LTQgICBjMC0xLjYsMC44LTIuNSwyLjQtMi41aDkuOGMxLjksMCwzLjIsMC4zLDMuOSwxYzAuOCwwLjYsMS40LDIsMiwzLjlsMTYuOCw2Ni4ybDE1LjYtNjYuMmMwLjUtMiwxLjEtMy4zLDEuOS0zLjljMC44LTAuNiwyLjItMSw0LTEgICBoOGMxLjksMCwzLjIsMC4zLDQsMWMwLjgsMC42LDEuNSwyLDEuOSwzLjlsMTUuOCw2N2wxNy4zLTY3YzAuNi0yLDEuMy0zLjMsMi0zLjljMC44LTAuNiwyLjEtMSwzLjktMWg5LjNjMS42LDAsMi41LDAuOCwyLjUsMi41ICAgYzAsMC41LTAuMSwxLTAuMiwxLjZjLTAuMSwwLjYtMC4zLDEuNC0wLjcsMi41bC0yNC4xLDc3LjNjLTAuNiwyLTEuMywzLjMtMi4xLDMuOWMtMC44LDAuNi0yLjEsMS0zLjgsMWgtOC42Yy0xLjksMC0zLjItMC4zLTQtMSAgIGMtMC44LTAuNy0xLjUtMi0xLjktNEwxNTYsMjNsLTE1LjQsNjQuNGMtMC41LDItMS4xLDMuMy0xLjksNGMtMC44LDAuNy0yLjIsMS00LDFIMTI2LjF6IE0yNTQuNiw5NS4xYy01LjIsMC0xMC40LTAuNi0xNS40LTEuOCAgIGMtNS0xLjItOC45LTIuNS0xMS41LTRjLTEuNi0wLjktMi43LTEuOS0zLjEtMi44Yy0wLjQtMC45LTAuNi0xLjktMC42LTIuOHYtNS4xYzAtMi4xLDAuOC0zLjEsMi4zLTMuMWMwLjYsMCwxLjIsMC4xLDEuOCwwLjMgICBjMC42LDAuMiwxLjUsMC42LDIuNSwxYzMuNCwxLjUsNy4xLDIuNywxMSwzLjVjNCwwLjgsNy45LDEuMiwxMS45LDEuMmM2LjMsMCwxMS4yLTEuMSwxNC42LTMuM2MzLjQtMi4yLDUuMi01LjQsNS4yLTkuNSAgIGMwLTIuOC0wLjktNS4xLTIuNy03Yy0xLjgtMS45LTUuMi0zLjYtMTAuMS01LjJMMjQ2LDUyYy03LjMtMi4zLTEyLjctNS43LTE2LTEwLjJjLTMuMy00LjQtNS05LjMtNS0xNC41YzAtNC4yLDAuOS03LjksMi43LTExLjEgICBjMS44LTMuMiw0LjItNiw3LjItOC4yYzMtMi4zLDYuNC00LDEwLjQtNS4yYzQtMS4yLDguMi0xLjcsMTIuNi0xLjdjMi4yLDAsNC41LDAuMSw2LjcsMC40YzIuMywwLjMsNC40LDAuNyw2LjUsMS4xICAgYzIsMC41LDMuOSwxLDUuNywxLjZjMS44LDAuNiwzLjIsMS4yLDQuMiwxLjhjMS40LDAuOCwyLjQsMS42LDMsMi41YzAuNiwwLjgsMC45LDEuOSwwLjksMy4zdjQuN2MwLDIuMS0wLjgsMy4yLTIuMywzLjIgICBjLTAuOCwwLTIuMS0wLjQtMy44LTEuMmMtNS43LTIuNi0xMi4xLTMuOS0xOS4yLTMuOWMtNS43LDAtMTAuMiwwLjktMTMuMywyLjhjLTMuMSwxLjktNC43LDQuOC00LjcsOC45YzAsMi44LDEsNS4yLDMsNy4xICAgYzIsMS45LDUuNywzLjgsMTEsNS41bDE0LjIsNC41YzcuMiwyLjMsMTIuNCw1LjUsMTUuNSw5LjZjMy4xLDQuMSw0LjYsOC44LDQuNiwxNGMwLDQuMy0wLjksOC4yLTIuNiwxMS42ICAgYy0xLjgsMy40LTQuMiw2LjQtNy4zLDguOGMtMy4xLDIuNS02LjgsNC4zLTExLjEsNS42QzI2NC40LDk0LjQsMjU5LjcsOTUuMSwyNTQuNiw5NS4xeiIvPgoJPGc+CgkJPHBhdGggY2xhc3M9InN0MSIgZD0iTTI3My41LDE0My43Yy0zMi45LDI0LjMtODAuNywzNy4yLTEyMS44LDM3LjJjLTU3LjYsMC0xMDkuNS0yMS4zLTE0OC43LTU2LjdjLTMuMS0yLjgtMC4zLTYuNiwzLjQtNC40ICAgIGM0Mi40LDI0LjYsOTQuNywzOS41LDE0OC44LDM5LjVjMzYuNSwwLDc2LjYtNy42LDExMy41LTIzLjJDMjc0LjIsMTMzLjYsMjc4LjksMTM5LjcsMjczLjUsMTQzLjd6Ii8+CgkJPHBhdGggY2xhc3M9InN0MSIgZD0iTTI4Ny4yLDEyOC4xYy00LjItNS40LTI3LjgtMi42LTM4LjUtMS4zYy0zLjIsMC40LTMuNy0yLjQtMC44LTQuNWMxOC44LTEzLjIsNDkuNy05LjQsNTMuMy01ICAgIGMzLjYsNC41LTEsMzUuNC0xOC42LDUwLjJjLTIuNywyLjMtNS4zLDEuMS00LjEtMS45QzI4Mi41LDE1NS43LDI5MS40LDEzMy40LDI4Ny4yLDEyOC4xeiIvPgoJPC9nPgo8L2c+Cjwvc3ZnPg== + mediatype: image/svg+xml + install: + spec: + clusterPermissions: + - rules: + - apiGroups: + - "" + resources: + - configmaps + verbs: + - get + - list + - patch + - watch + - apiGroups: + - "" + resources: + - namespaces + verbs: + - get + - list + - watch + - apiGroups: + - "" + resources: + - secrets + verbs: + - get + - list + - patch + - watch + - apiGroups: + - ecs.services.k8s.aws + resources: + - clusters + verbs: + - create + - delete + - get + - list + - patch + - update + - watch + - apiGroups: + - ecs.services.k8s.aws + resources: + - clusters/status + verbs: + - get + - patch + - update + - apiGroups: + - ecs.services.k8s.aws + resources: + - services + verbs: + - create + - delete + - get + - list + - patch + - update + - watch + - apiGroups: + - ecs.services.k8s.aws + resources: + - services/status + verbs: + - get + - patch + - update + - apiGroups: + - ecs.services.k8s.aws + resources: + - taskdefinitions + verbs: + - create + - delete + - get + - list + - patch + - update + - watch + - apiGroups: + - ecs.services.k8s.aws + resources: + - taskdefinitions/status + verbs: + - get + - patch + - update + - apiGroups: + - iam.services.k8s.aws + resources: + - roles + verbs: + - get + - list + - apiGroups: + - iam.services.k8s.aws + resources: + - roles/status + verbs: + - get + - list + - apiGroups: + - services.k8s.aws + resources: + - adoptedresources + verbs: + - create + - delete + - get + - list + - patch + - update + - watch + - apiGroups: + - services.k8s.aws + resources: + - adoptedresources/status + verbs: + - get + - patch + - update + - apiGroups: + - services.k8s.aws + resources: + - fieldexports + verbs: + - create + - delete + - get + - list + - patch + - update + - watch + - apiGroups: + - services.k8s.aws + resources: + - fieldexports/status + verbs: + - get + - patch + - update + serviceAccountName: ack-ecs-controller + deployments: + - label: + app.kubernetes.io/name: ack-ecs-controller + app.kubernetes.io/part-of: ack-system + name: ack-ecs-controller + spec: + replicas: 1 + selector: + matchLabels: + app.kubernetes.io/name: ack-ecs-controller + strategy: {} + template: + metadata: + labels: + app.kubernetes.io/name: ack-ecs-controller + spec: + containers: + - args: + - --aws-region + - $(AWS_REGION) + - --aws-endpoint-url + - $(AWS_ENDPOINT_URL) + - --enable-development-logging=$(ACK_ENABLE_DEVELOPMENT_LOGGING) + - --log-level + - $(ACK_LOG_LEVEL) + - --resource-tags + - $(ACK_RESOURCE_TAGS) + - --watch-namespace + - $(ACK_WATCH_NAMESPACE) + - --enable-leader-election=$(ENABLE_LEADER_ELECTION) + - --leader-election-namespace + - $(LEADER_ELECTION_NAMESPACE) + - --reconcile-default-max-concurrent-syncs + - $(RECONCILE_DEFAULT_MAX_CONCURRENT_SYNCS) + command: + - ./bin/controller + env: + - name: ACK_SYSTEM_NAMESPACE + valueFrom: + fieldRef: + fieldPath: metadata.namespace + envFrom: + - configMapRef: + name: ack-ecs-user-config + optional: false + - secretRef: + name: ack-ecs-user-secrets + optional: true + image: public.ecr.aws/aws-controllers-k8s/ecs-controller:0.0.8 + livenessProbe: + httpGet: + path: /healthz + port: 8081 + initialDelaySeconds: 15 + periodSeconds: 20 + name: controller + ports: + - containerPort: 8080 + name: http + readinessProbe: + httpGet: + path: /readyz + port: 8081 + initialDelaySeconds: 5 + periodSeconds: 10 + resources: + limits: + cpu: 100m + memory: 300Mi + requests: + cpu: 100m + memory: 200Mi + securityContext: + allowPrivilegeEscalation: false + capabilities: + drop: + - ALL + privileged: false + runAsNonRoot: true + dnsPolicy: ClusterFirst + securityContext: + seccompProfile: + type: RuntimeDefault + serviceAccountName: ack-ecs-controller + terminationGracePeriodSeconds: 10 + permissions: + - rules: + - apiGroups: + - coordination.k8s.io + resources: + - leases + verbs: + - get + - list + - watch + - create + - update + - patch + - delete + - apiGroups: + - "" + resources: + - events + verbs: + - create + - patch + serviceAccountName: ack-ecs-controller + strategy: deployment + installModes: + - supported: true + type: OwnNamespace + - supported: true + type: SingleNamespace + - supported: true + type: MultiNamespace + - supported: true + type: AllNamespaces + keywords: + - ecs + - aws + - amazon + - ack + links: + - name: AWS Controllers for Kubernetes + url: https://github.com/aws-controllers-k8s/community + - name: Documentation + url: https://aws-controllers-k8s.github.io/community/ + - name: Amazon ECS Developer Resources + url: https://aws.amazon.com/ecs/resources/ + maintainers: + - email: ack-maintainers@amazon.com + name: ecs maintainer team + maturity: alpha + provider: + name: Amazon, Inc. + url: https://aws.amazon.com + version: 0.0.8 diff --git a/operators/ack-ecs-controller/0.0.8/manifests/ack-ecs-metrics-service_v1_service.yaml b/operators/ack-ecs-controller/0.0.8/manifests/ack-ecs-metrics-service_v1_service.yaml new file mode 100644 index 00000000000..c0e8e68708b --- /dev/null +++ b/operators/ack-ecs-controller/0.0.8/manifests/ack-ecs-metrics-service_v1_service.yaml @@ -0,0 +1,16 @@ +apiVersion: v1 +kind: Service +metadata: + creationTimestamp: null + name: ack-ecs-metrics-service +spec: + ports: + - name: metricsport + port: 8080 + protocol: TCP + targetPort: http + selector: + app.kubernetes.io/name: ack-ecs-controller + type: NodePort +status: + loadBalancer: {} diff --git a/operators/ack-ecs-controller/0.0.8/manifests/ack-ecs-reader_rbac.authorization.k8s.io_v1_role.yaml b/operators/ack-ecs-controller/0.0.8/manifests/ack-ecs-reader_rbac.authorization.k8s.io_v1_role.yaml new file mode 100644 index 00000000000..7682d36f717 --- /dev/null +++ b/operators/ack-ecs-controller/0.0.8/manifests/ack-ecs-reader_rbac.authorization.k8s.io_v1_role.yaml @@ -0,0 +1,16 @@ +apiVersion: rbac.authorization.k8s.io/v1 +kind: Role +metadata: + creationTimestamp: null + name: ack-ecs-reader +rules: +- apiGroups: + - ecs.services.k8s.aws + resources: + - clusters + - services + - taskdefinitions + verbs: + - get + - list + - watch diff --git a/operators/ack-ecs-controller/0.0.8/manifests/ack-ecs-writer_rbac.authorization.k8s.io_v1_role.yaml b/operators/ack-ecs-controller/0.0.8/manifests/ack-ecs-writer_rbac.authorization.k8s.io_v1_role.yaml new file mode 100644 index 00000000000..00374e1b3b7 --- /dev/null +++ b/operators/ack-ecs-controller/0.0.8/manifests/ack-ecs-writer_rbac.authorization.k8s.io_v1_role.yaml @@ -0,0 +1,30 @@ +apiVersion: rbac.authorization.k8s.io/v1 +kind: Role +metadata: + creationTimestamp: null + name: ack-ecs-writer +rules: +- apiGroups: + - ecs.services.k8s.aws + resources: + - clusters + - services + - taskdefinitions + verbs: + - create + - delete + - get + - list + - patch + - update + - watch +- apiGroups: + - ecs.services.k8s.aws + resources: + - clusters + - services + - taskdefinitions + verbs: + - get + - patch + - update diff --git a/operators/ack-ecs-controller/0.0.8/manifests/ecs.services.k8s.aws_clusters.yaml b/operators/ack-ecs-controller/0.0.8/manifests/ecs.services.k8s.aws_clusters.yaml new file mode 100644 index 00000000000..d89f62eee21 --- /dev/null +++ b/operators/ack-ecs-controller/0.0.8/manifests/ecs.services.k8s.aws_clusters.yaml @@ -0,0 +1,522 @@ +apiVersion: apiextensions.k8s.io/v1 +kind: CustomResourceDefinition +metadata: + annotations: + controller-gen.kubebuilder.io/version: v0.14.0 + creationTimestamp: null + name: clusters.ecs.services.k8s.aws +spec: + group: ecs.services.k8s.aws + names: + kind: Cluster + listKind: ClusterList + plural: clusters + singular: cluster + scope: Namespaced + versions: + - additionalPrinterColumns: + - jsonPath: .status.activeServicesCount + name: ACTIVESERVICES + type: integer + - jsonPath: .spec.name + name: CLUSTER + type: string + - jsonPath: .status.pendingTasksCount + name: PENDINGTASKS + type: integer + - jsonPath: .status.runningTasksCount + name: RUNNINGTASKS + type: integer + - jsonPath: .status.status + name: STATUS + type: string + name: v1alpha1 + schema: + openAPIV3Schema: + description: Cluster is the Schema for the Clusters API + properties: + apiVersion: + description: |- + APIVersion defines the versioned schema of this representation of an object. + Servers should convert recognized schemas to the latest internal value, and + may reject unrecognized values. + More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources + type: string + kind: + description: |- + Kind is a string value representing the REST resource this object represents. + Servers may infer this from the endpoint the client submits requests to. + Cannot be updated. + In CamelCase. + More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds + type: string + metadata: + type: object + spec: + description: |- + ClusterSpec defines the desired state of Cluster. + + + A regional grouping of one or more container instances where you can run + task requests. Each account receives a default cluster the first time you + use the Amazon ECS service, but you may also create other clusters. Clusters + may contain more than one instance type simultaneously. + properties: + capacityProviders: + description: |- + The short name of one or more capacity providers to associate with the cluster. + A capacity provider must be associated with a cluster before it can be included + as part of the default capacity provider strategy of the cluster or used + in a capacity provider strategy when calling the CreateService (https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateService.html) + or RunTask (https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_RunTask.html) + actions. + + + If specifying a capacity provider that uses an Auto Scaling group, the capacity + provider must be created but not associated with another cluster. New Auto + Scaling group capacity providers can be created with the CreateCapacityProvider + (https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateCapacityProvider.html) + API operation. + + + To use a Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT + capacity providers. The Fargate capacity providers are available to all accounts + and only need to be associated with a cluster to be used. + + + The PutCapacityProvider (https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutCapacityProvider.html) + API operation is used to update the list of available capacity providers + for a cluster after the cluster is created. + items: + type: string + type: array + configuration: + description: The execute command configuration for the cluster. + properties: + executeCommandConfiguration: + description: The details of the execute command configuration. + properties: + kmsKeyID: + type: string + logConfiguration: + description: |- + The log configuration for the results of the execute command actions. The + logs can be sent to CloudWatch Logs or an Amazon S3 bucket. + properties: + cloudWatchEncryptionEnabled: + type: boolean + cloudWatchLogGroupName: + type: string + s3BucketName: + type: string + s3EncryptionEnabled: + type: boolean + s3KeyPrefix: + type: string + type: object + logging: + type: string + type: object + type: object + defaultCapacityProviderStrategy: + description: |- + The capacity provider strategy to set as the default for the cluster. After + a default capacity provider strategy is set for a cluster, when you call + the CreateService (https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateService.html) + or RunTask (https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_RunTask.html) + APIs with no capacity provider strategy or launch type specified, the default + capacity provider strategy for the cluster is used. + + + If a default capacity provider strategy isn't defined for a cluster when + it was created, it can be defined later with the PutClusterCapacityProviders + API operation. + items: + description: |- + The details of a capacity provider strategy. A capacity provider strategy + can be set when using the RunTask or CreateCluster APIs or as the default + capacity provider strategy for a cluster with the CreateCluster API. + + + Only capacity providers that are already associated with a cluster and have + an ACTIVE or UPDATING status can be used in a capacity provider strategy. + The PutClusterCapacityProviders API is used to associate a capacity provider + with a cluster. + + + If specifying a capacity provider that uses an Auto Scaling group, the capacity + provider must already be created. New Auto Scaling group capacity providers + can be created with the CreateCapacityProvider API operation. + + + To use a Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT + capacity providers. The Fargate capacity providers are available to all accounts + and only need to be associated with a cluster to be used in a capacity provider + strategy. + + + A capacity provider strategy may contain a maximum of 6 capacity providers. + properties: + base: + format: int64 + type: integer + capacityProvider: + type: string + weight: + format: int64 + type: integer + type: object + type: array + name: + description: |- + The name of your cluster. If you don't specify a name for your cluster, you + create a cluster that's named default. Up to 255 letters (uppercase and lowercase), + numbers, underscores, and hyphens are allowed. + type: string + serviceConnectDefaults: + description: |- + Use this parameter to set a default Service Connect namespace. After you + set a default Service Connect namespace, any new services with Service Connect + turned on that are created in the cluster are added as client services in + the namespace. This setting only applies to new services that set the enabled + parameter to true in the ServiceConnectConfiguration. You can set the namespace + of each service individually in the ServiceConnectConfiguration to override + this default parameter. + + + Tasks that run in a namespace can use short names to connect to services + in the namespace. Tasks can connect to services across all of the clusters + in the namespace. Tasks connect through a managed proxy container that collects + logs and metrics for increased visibility. Only the tasks that Amazon ECS + services create are supported with Service Connect. For more information, + see Service Connect (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html) + in the Amazon Elastic Container Service Developer Guide. + properties: + namespace: + type: string + type: object + settings: + description: |- + The setting to use when creating a cluster. This parameter is used to turn + on CloudWatch Container Insights for a cluster. If this value is specified, + it overrides the containerInsights value set with PutAccountSetting or PutAccountSettingDefault. + items: + description: |- + The settings to use when creating a cluster. This parameter is used to turn + on CloudWatch Container Insights for a cluster. + properties: + name: + type: string + value: + type: string + type: object + type: array + tags: + description: |- + The metadata that you apply to the cluster to help you categorize and organize + them. Each tag consists of a key and an optional value. You define both. + + + The following basic restrictions apply to tags: + + + * Maximum number of tags per resource - 50 + + + * For each resource, each tag key must be unique, and each tag key can + have only one value. + + + * Maximum key length - 128 Unicode characters in UTF-8 + + + * Maximum value length - 256 Unicode characters in UTF-8 + + + * If your tagging schema is used across multiple services and resources, + remember that other services may have restrictions on allowed characters. + Generally allowed characters are: letters, numbers, and spaces representable + in UTF-8, and the following characters: + - = . _ : / @. + + + * Tag keys and values are case-sensitive. + + + * Do not use aws:, AWS:, or any upper or lowercase combination of such + as a prefix for either keys or values as it is reserved for Amazon Web + Services use. You cannot edit or delete tag keys or values with this prefix. + Tags with this prefix do not count against your tags per resource limit. + items: + description: |- + The metadata that you apply to a resource to help you categorize and organize + them. Each tag consists of a key and an optional value. You define them. + + + The following basic restrictions apply to tags: + + + * Maximum number of tags per resource - 50 + + + * For each resource, each tag key must be unique, and each tag key can + have only one value. + + + * Maximum key length - 128 Unicode characters in UTF-8 + + + * Maximum value length - 256 Unicode characters in UTF-8 + + + * If your tagging schema is used across multiple services and resources, + remember that other services may have restrictions on allowed characters. + Generally allowed characters are: letters, numbers, and spaces representable + in UTF-8, and the following characters: + - = . _ : / @. + + + * Tag keys and values are case-sensitive. + + + * Do not use aws:, AWS:, or any upper or lowercase combination of such + as a prefix for either keys or values as it is reserved for Amazon Web + Services use. You cannot edit or delete tag keys or values with this prefix. + Tags with this prefix do not count against your tags per resource limit. + properties: + key: + type: string + value: + type: string + type: object + type: array + type: object + status: + description: ClusterStatus defines the observed state of Cluster + properties: + ackResourceMetadata: + description: |- + All CRs managed by ACK have a common `Status.ACKResourceMetadata` member + that is used to contain resource sync state, account ownership, + constructed ARN for the resource + properties: + arn: + description: |- + ARN is the Amazon Resource Name for the resource. This is a + globally-unique identifier and is set only by the ACK service controller + once the controller has orchestrated the creation of the resource OR + when it has verified that an "adopted" resource (a resource where the + ARN annotation was set by the Kubernetes user on the CR) exists and + matches the supplied CR's Spec field values. + TODO(vijat@): Find a better strategy for resources that do not have ARN in CreateOutputResponse + https://github.com/aws/aws-controllers-k8s/issues/270 + type: string + ownerAccountID: + description: |- + OwnerAccountID is the AWS Account ID of the account that owns the + backend AWS service API resource. + type: string + region: + description: Region is the AWS region in which the resource exists + or will exist. + type: string + required: + - ownerAccountID + - region + type: object + activeServicesCount: + description: |- + The number of services that are running on the cluster in an ACTIVE state. + You can view these services with ListServices. + format: int64 + type: integer + attachments: + description: |- + The resources attached to a cluster. When using a capacity provider with + a cluster, the capacity provider and associated resources are returned as + cluster attachments. + items: + description: An object representing a container instance or task + attachment. + properties: + details: + items: + description: A key-value pair object. + properties: + name: + type: string + value: + type: string + type: object + type: array + id: + type: string + status: + type: string + type: + type: string + type: object + type: array + attachmentsStatus: + description: |- + The status of the capacity providers associated with the cluster. The following + are the states that are returned. + + + UPDATE_IN_PROGRESS + + + The available capacity providers for the cluster are updating. + + + UPDATE_COMPLETE + + + The capacity providers have successfully updated. + + + UPDATE_FAILED + + + The capacity provider updates failed. + type: string + conditions: + description: |- + All CRS managed by ACK have a common `Status.Conditions` member that + contains a collection of `ackv1alpha1.Condition` objects that describe + the various terminal states of the CR and its backend AWS service API + resource + items: + description: |- + Condition is the common struct used by all CRDs managed by ACK service + controllers to indicate terminal states of the CR and its backend AWS + service API resource + properties: + lastTransitionTime: + description: Last time the condition transitioned from one status + to another. + format: date-time + type: string + message: + description: A human readable message indicating details about + the transition. + type: string + reason: + description: The reason for the condition's last transition. + type: string + status: + description: Status of the condition, one of True, False, Unknown. + type: string + type: + description: Type is the type of the Condition + type: string + required: + - status + - type + type: object + type: array + pendingTasksCount: + description: The number of tasks in the cluster that are in the PENDING + state. + format: int64 + type: integer + registeredContainerInstancesCount: + description: |- + The number of container instances registered into the cluster. This includes + container instances in both ACTIVE and DRAINING status. + format: int64 + type: integer + runningTasksCount: + description: The number of tasks in the cluster that are in the RUNNING + state. + format: int64 + type: integer + statistics: + description: |- + Additional information about your clusters that are separated by launch type. + They include the following: + + + * runningEC2TasksCount + + + * RunningFargateTasksCount + + + * pendingEC2TasksCount + + + * pendingFargateTasksCount + + + * activeEC2ServiceCount + + + * activeFargateServiceCount + + + * drainingEC2ServiceCount + + + * drainingFargateServiceCount + items: + description: A key-value pair object. + properties: + name: + type: string + value: + type: string + type: object + type: array + status: + description: |- + The status of the cluster. The following are the possible states that are + returned. + + + ACTIVE + + + The cluster is ready to accept tasks and if applicable you can register container + instances with the cluster. + + + PROVISIONING + + + The cluster has capacity providers that are associated with it and the resources + needed for the capacity provider are being created. + + + DEPROVISIONING + + + The cluster has capacity providers that are associated with it and the resources + needed for the capacity provider are being deleted. + + + FAILED + + + The cluster has capacity providers that are associated with it and the resources + needed for the capacity provider have failed to create. + + + INACTIVE + + + The cluster has been deleted. Clusters with an INACTIVE status may remain + discoverable in your account for a period of time. However, this behavior + is subject to change in the future. We don't recommend that you rely on INACTIVE + clusters persisting. + type: string + type: object + type: object + served: true + storage: true + subresources: + status: {} +status: + acceptedNames: + kind: "" + plural: "" + conditions: null + storedVersions: null diff --git a/operators/ack-ecs-controller/0.0.8/manifests/ecs.services.k8s.aws_services.yaml b/operators/ack-ecs-controller/0.0.8/manifests/ecs.services.k8s.aws_services.yaml new file mode 100644 index 00000000000..522b8049658 --- /dev/null +++ b/operators/ack-ecs-controller/0.0.8/manifests/ecs.services.k8s.aws_services.yaml @@ -0,0 +1,1686 @@ +apiVersion: apiextensions.k8s.io/v1 +kind: CustomResourceDefinition +metadata: + annotations: + controller-gen.kubebuilder.io/version: v0.14.0 + creationTimestamp: null + name: services.ecs.services.k8s.aws +spec: + group: ecs.services.k8s.aws + names: + kind: Service + listKind: ServiceList + plural: services + singular: service + scope: Namespaced + versions: + - additionalPrinterColumns: + - jsonPath: .spec.cluster + name: CLUSTER + type: string + - jsonPath: .spec.desiredCount + name: DESIRED + type: integer + - jsonPath: .status.pendingCount + name: PENDING + type: integer + - jsonPath: .status.runningCount + name: RUNNING + type: integer + - jsonPath: .spec.name + name: SERVICE + type: string + - jsonPath: .status.status + name: STATUS + type: string + - jsonPath: .spec.taskDefinition + name: TASKDEFINITION + type: string + name: v1alpha1 + schema: + openAPIV3Schema: + description: Service is the Schema for the Services API + properties: + apiVersion: + description: |- + APIVersion defines the versioned schema of this representation of an object. + Servers should convert recognized schemas to the latest internal value, and + may reject unrecognized values. + More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources + type: string + kind: + description: |- + Kind is a string value representing the REST resource this object represents. + Servers may infer this from the endpoint the client submits requests to. + Cannot be updated. + In CamelCase. + More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds + type: string + metadata: + type: object + spec: + description: |- + ServiceSpec defines the desired state of Service. + + + Details on a service within a cluster. + properties: + capacityProviderStrategy: + description: |- + The capacity provider strategy to use for the service. + + + If a capacityProviderStrategy is specified, the launchType parameter must + be omitted. If no capacityProviderStrategy or launchType is specified, the + defaultCapacityProviderStrategy for the cluster is used. + + + A capacity provider strategy may contain a maximum of 6 capacity providers. + items: + description: |- + The details of a capacity provider strategy. A capacity provider strategy + can be set when using the RunTask or CreateCluster APIs or as the default + capacity provider strategy for a cluster with the CreateCluster API. + + + Only capacity providers that are already associated with a cluster and have + an ACTIVE or UPDATING status can be used in a capacity provider strategy. + The PutClusterCapacityProviders API is used to associate a capacity provider + with a cluster. + + + If specifying a capacity provider that uses an Auto Scaling group, the capacity + provider must already be created. New Auto Scaling group capacity providers + can be created with the CreateCapacityProvider API operation. + + + To use a Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT + capacity providers. The Fargate capacity providers are available to all accounts + and only need to be associated with a cluster to be used in a capacity provider + strategy. + + + A capacity provider strategy may contain a maximum of 6 capacity providers. + properties: + base: + format: int64 + type: integer + capacityProvider: + type: string + weight: + format: int64 + type: integer + type: object + type: array + cluster: + description: |- + The short name or full Amazon Resource Name (ARN) of the cluster that you + run your service on. If you do not specify a cluster, the default cluster + is assumed. + type: string + clusterRef: + description: "AWSResourceReferenceWrapper provides a wrapper around + *AWSResourceReference\ntype to provide more user friendly syntax + for references using 'from' field\nEx:\nAPIIDRef:\n\n\n\tfrom:\n\t + \ name: my-api" + properties: + from: + description: |- + AWSResourceReference provides all the values necessary to reference another + k8s resource for finding the identifier(Id/ARN/Name) + properties: + name: + type: string + namespace: + type: string + type: object + type: object + deploymentConfiguration: + description: |- + Optional deployment parameters that control how many tasks run during the + deployment and the ordering of stopping and starting tasks. + properties: + alarms: + description: |- + One of the methods which provide a way for you to quickly identify when a + deployment has failed, and then to optionally roll back the failure to the + last working deployment. + + + When the alarms are generated, Amazon ECS sets the service deployment to + failed. Set the rollback parameter to have Amazon ECS to roll back your service + to the last completed deployment after a failure. + + + You can only use the DeploymentAlarms method to detect failures when the + DeploymentController is set to ECS (rolling update). + + + For more information, see Rolling update (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-type-ecs.html) + in the Amazon Elastic Container Service Developer Guide . + properties: + alarmNames: + items: + type: string + type: array + enable: + type: boolean + rollback: + type: boolean + type: object + deploymentCircuitBreaker: + description: |- + The deployment circuit breaker can only be used for services using the rolling + update (ECS) deployment type. + + + The deployment circuit breaker determines whether a service deployment will + fail if the service can't reach a steady state. If it is turned on, a service + deployment will transition to a failed state and stop launching new tasks. + You can also configure Amazon ECS to roll back your service to the last completed + deployment after a failure. For more information, see Rolling update (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-type-ecs.html) + in the Amazon Elastic Container Service Developer Guide. + + + For more information about API failure reasons, see API failure reasons (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/api_failures_messages.html) + in the Amazon Elastic Container Service Developer Guide. + properties: + enable: + type: boolean + rollback: + type: boolean + type: object + maximumPercent: + format: int64 + type: integer + minimumHealthyPercent: + format: int64 + type: integer + type: object + deploymentController: + description: |- + The deployment controller to use for the service. If no deployment controller + is specified, the default value of ECS is used. + properties: + type: + type: string + type: object + desiredCount: + description: |- + The number of instantiations of the specified task definition to place and + keep running in your service. + + + This is required if schedulingStrategy is REPLICA or isn't specified. If + schedulingStrategy is DAEMON then this isn't required. + format: int64 + type: integer + enableECSManagedTags: + description: |- + Specifies whether to turn on Amazon ECS managed tags for the tasks within + the service. For more information, see Tagging your Amazon ECS resources + (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-using-tags.html) + in the Amazon Elastic Container Service Developer Guide. + + + When you use Amazon ECS managed tags, you need to set the propagateTags request + parameter. + type: boolean + enableExecuteCommand: + description: |- + Determines whether the execute command functionality is turned on for the + service. If true, this enables execute command functionality on all containers + in the service tasks. + type: boolean + healthCheckGracePeriodSeconds: + description: |- + The period of time, in seconds, that the Amazon ECS service scheduler ignores + unhealthy Elastic Load Balancing target health checks after a task has first + started. This is only used when your service is configured to use a load + balancer. If your service has a load balancer defined and you don't specify + a health check grace period value, the default value of 0 is used. + + + If you do not use an Elastic Load Balancing, we recommend that you use the + startPeriod in the task definition health check parameters. For more information, + see Health check (https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_HealthCheck.html). + + + If your service's tasks take a while to start and respond to Elastic Load + Balancing health checks, you can specify a health check grace period of up + to 2,147,483,647 seconds (about 69 years). During that time, the Amazon ECS + service scheduler ignores health check status. This grace period can prevent + the service scheduler from marking tasks as unhealthy and stopping them before + they have time to come up. + format: int64 + type: integer + launchType: + description: |- + The infrastructure that you run your service on. For more information, see + Amazon ECS launch types (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_types.html) + in the Amazon Elastic Container Service Developer Guide. + + + The FARGATE launch type runs your tasks on Fargate On-Demand infrastructure. + + + Fargate Spot infrastructure is available for use but a capacity provider + strategy must be used. For more information, see Fargate capacity providers + (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/fargate-capacity-providers.html) + in the Amazon ECS User Guide for Fargate. + + + The EC2 launch type runs your tasks on Amazon EC2 instances registered to + your cluster. + + + The EXTERNAL launch type runs your tasks on your on-premises server or virtual + machine (VM) capacity registered to your cluster. + + + A service can use either a launch type or a capacity provider strategy. If + a launchType is specified, the capacityProviderStrategy parameter must be + omitted. + type: string + loadBalancers: + description: |- + A load balancer object representing the load balancers to use with your service. + For more information, see Service load balancing (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-load-balancing.html) + in the Amazon Elastic Container Service Developer Guide. + + + If the service uses the rolling update (ECS) deployment controller and using + either an Application Load Balancer or Network Load Balancer, you must specify + one or more target group ARNs to attach to the service. The service-linked + role is required for services that use multiple target groups. For more information, + see Using service-linked roles for Amazon ECS (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html) + in the Amazon Elastic Container Service Developer Guide. + + + If the service uses the CODE_DEPLOY deployment controller, the service is + required to use either an Application Load Balancer or Network Load Balancer. + When creating an CodeDeploy deployment group, you specify two target groups + (referred to as a targetGroupPair). During a deployment, CodeDeploy determines + which task set in your service has the status PRIMARY, and it associates + one target group with it. Then, it also associates the other target group + with the replacement task set. The load balancer can also have up to two + listeners: a required listener for production traffic and an optional listener + that you can use to perform validation tests with Lambda functions before + routing production traffic to it. + + + If you use the CODE_DEPLOY deployment controller, these values can be changed + when updating the service. + + + For Application Load Balancers and Network Load Balancers, this object must + contain the load balancer target group ARN, the container name, and the container + port to access from the load balancer. The container name must be as it appears + in a container definition. The load balancer name parameter must be omitted. + When a task from this service is placed on a container instance, the container + instance and port combination is registered as a target in the target group + that's specified here. + + + For Classic Load Balancers, this object must contain the load balancer name, + the container name , and the container port to access from the load balancer. + The container name must be as it appears in a container definition. The target + group ARN parameter must be omitted. When a task from this service is placed + on a container instance, the container instance is registered with the load + balancer that's specified here. + + + Services with tasks that use the awsvpc network mode (for example, those + with the Fargate launch type) only support Application Load Balancers and + Network Load Balancers. Classic Load Balancers aren't supported. Also, when + you create any target groups for these services, you must choose ip as the + target type, not instance. This is because tasks that use the awsvpc network + mode are associated with an elastic network interface, not an Amazon EC2 + instance. + items: + description: |- + The load balancer configuration to use with a service or task set. + + + When you add, update, or remove a load balancer configuration, Amazon ECS + starts a new deployment with the updated Elastic Load Balancing configuration. + This causes tasks to register to and deregister from load balancers. + + + We recommend that you verify this on a test environment before you update + the Elastic Load Balancing configuration. + + + A service-linked role is required for services that use multiple target groups. + For more information, see Using service-linked roles (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html) + in the Amazon Elastic Container Service Developer Guide. + properties: + containerName: + type: string + containerPort: + format: int64 + type: integer + loadBalancerName: + type: string + targetGroupARN: + type: string + type: object + type: array + name: + description: |- + The name of your service. Up to 255 letters (uppercase and lowercase), numbers, + underscores, and hyphens are allowed. Service names must be unique within + a cluster, but you can have similarly named services in multiple clusters + within a Region or across multiple Regions. + type: string + networkConfiguration: + description: |- + The network configuration for the service. This parameter is required for + task definitions that use the awsvpc network mode to receive their own elastic + network interface, and it isn't supported for other network modes. For more + information, see Task networking (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-networking.html) + in the Amazon Elastic Container Service Developer Guide. + properties: + awsVPCConfiguration: + description: |- + An object representing the networking details for a task or service. For + example awsvpcConfiguration={subnets=["subnet-12344321"],securityGroups=["sg-12344321"]} + properties: + assignPublicIP: + type: string + securityGroups: + items: + type: string + type: array + subnets: + items: + type: string + type: array + type: object + type: object + placementConstraints: + description: |- + An array of placement constraint objects to use for tasks in your service. + You can specify a maximum of 10 constraints for each task. This limit includes + constraints in the task definition and those specified at runtime. + items: + description: |- + An object representing a constraint on task placement. For more information, + see Task placement constraints (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement-constraints.html) + in the Amazon Elastic Container Service Developer Guide. + + + If you're using the Fargate launch type, task placement constraints aren't + supported. + properties: + expression: + type: string + type: + type: string + type: object + type: array + placementStrategy: + description: |- + The placement strategy objects to use for tasks in your service. You can + specify a maximum of 5 strategy rules for each service. + items: + description: |- + The task placement strategy for a task or service. For more information, + see Task placement strategies (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement-strategies.html) + in the Amazon Elastic Container Service Developer Guide. + properties: + field: + type: string + type: + type: string + type: object + type: array + platformVersion: + description: |- + The platform version that your tasks in the service are running on. A platform + version is specified only for tasks using the Fargate launch type. If one + isn't specified, the LATEST platform version is used. For more information, + see Fargate platform versions (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html) + in the Amazon Elastic Container Service Developer Guide. + type: string + propagateTags: + description: |- + Specifies whether to propagate the tags from the task definition to the task. + If no value is specified, the tags aren't propagated. Tags can only be propagated + to the task during task creation. To add tags to a task after task creation, + use the TagResource (https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_TagResource.html) + API action. + + + The default is NONE. + type: string + role: + description: |- + The name or full Amazon Resource Name (ARN) of the IAM role that allows Amazon + ECS to make calls to your load balancer on your behalf. This parameter is + only permitted if you are using a load balancer with your service and your + task definition doesn't use the awsvpc network mode. If you specify the role + parameter, you must also specify a load balancer object with the loadBalancers + parameter. + + + If your account has already created the Amazon ECS service-linked role, that + role is used for your service unless you specify a role here. The service-linked + role is required if your task definition uses the awsvpc network mode or + if the service is configured to use service discovery, an external deployment + controller, multiple target groups, or Elastic Inference accelerators in + which case you don't specify a role here. For more information, see Using + service-linked roles for Amazon ECS (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html) + in the Amazon Elastic Container Service Developer Guide. + + + If your specified role has a path other than /, then you must either specify + the full role ARN (this is recommended) or prefix the role name with the + path. For example, if a role with the name bar has a path of /foo/ then you + would specify /foo/bar as the role name. For more information, see Friendly + names and paths (https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_identifiers.html#identifiers-friendly-names) + in the IAM User Guide. + type: string + roleRef: + description: "AWSResourceReferenceWrapper provides a wrapper around + *AWSResourceReference\ntype to provide more user friendly syntax + for references using 'from' field\nEx:\nAPIIDRef:\n\n\n\tfrom:\n\t + \ name: my-api" + properties: + from: + description: |- + AWSResourceReference provides all the values necessary to reference another + k8s resource for finding the identifier(Id/ARN/Name) + properties: + name: + type: string + namespace: + type: string + type: object + type: object + schedulingStrategy: + description: |- + The scheduling strategy to use for the service. For more information, see + Services (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html). + + + There are two service scheduler strategies available: + + + * REPLICA-The replica scheduling strategy places and maintains the desired + number of tasks across your cluster. By default, the service scheduler + spreads tasks across Availability Zones. You can use task placement strategies + and constraints to customize task placement decisions. This scheduler + strategy is required if the service uses the CODE_DEPLOY or EXTERNAL deployment + controller types. + + + * DAEMON-The daemon scheduling strategy deploys exactly one task on each + active container instance that meets all of the task placement constraints + that you specify in your cluster. The service scheduler also evaluates + the task placement constraints for running tasks and will stop tasks that + don't meet the placement constraints. When you're using this strategy, + you don't need to specify a desired number of tasks, a task placement + strategy, or use Service Auto Scaling policies. Tasks using the Fargate + launch type or the CODE_DEPLOY or EXTERNAL deployment controller types + don't support the DAEMON scheduling strategy. + type: string + serviceConnectConfiguration: + description: |- + The configuration for this service to discover and connect to services, and + be discovered by, and connected from, other services within a namespace. + + + Tasks that run in a namespace can use short names to connect to services + in the namespace. Tasks can connect to services across all of the clusters + in the namespace. Tasks connect through a managed proxy container that collects + logs and metrics for increased visibility. Only the tasks that Amazon ECS + services create are supported with Service Connect. For more information, + see Service Connect (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html) + in the Amazon Elastic Container Service Developer Guide. + properties: + enabled: + type: boolean + logConfiguration: + description: |- + The log configuration for the container. This parameter maps to LogConfig + in the Create a container (https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate) + section of the Docker Remote API (https://docs.docker.com/engine/api/v1.35/) + and the --log-driver option to docker run (https://docs.docker.com/engine/reference/commandline/run/). + + + By default, containers use the same logging driver that the Docker daemon + uses. However, the container might use a different logging driver than the + Docker daemon by specifying a log driver configuration in the container definition. + For more information about the options for different supported log drivers, + see Configure logging drivers (https://docs.docker.com/engine/admin/logging/overview/) + in the Docker documentation. + + + Understand the following when specifying a log configuration for your containers. + + + * Amazon ECS currently supports a subset of the logging drivers available + to the Docker daemon. Additional log drivers may be available in future + releases of the Amazon ECS container agent. For tasks on Fargate, the + supported log drivers are awslogs, splunk, and awsfirelens. For tasks + hosted on Amazon EC2 instances, the supported log drivers are awslogs, + fluentd, gelf, json-file, journald, logentries,syslog, splunk, and awsfirelens. + + + * This parameter requires version 1.18 of the Docker Remote API or greater + on your container instance. + + + * For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container + agent must register the available logging drivers with the ECS_AVAILABLE_LOGGING_DRIVERS + environment variable before containers placed on that instance can use + these log configuration options. For more information, see Amazon ECS + container agent configuration (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html) + in the Amazon Elastic Container Service Developer Guide. + + + * For tasks that are on Fargate, because you don't have access to the + underlying infrastructure your tasks are hosted on, any additional software + needed must be installed outside of the task. For example, the Fluentd + output aggregators or a remote host running Logstash to send Gelf logs + to. + properties: + logDriver: + type: string + options: + additionalProperties: + type: string + type: object + secretOptions: + items: + description: |- + An object representing the secret to expose to your container. Secrets can + be exposed to a container in the following ways: + + + * To inject sensitive data into your containers as environment variables, + use the secrets container definition parameter. + + + * To reference sensitive information in the log configuration of a container, + use the secretOptions container definition parameter. + + + For more information, see Specifying sensitive data (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/specifying-sensitive-data.html) + in the Amazon Elastic Container Service Developer Guide. + properties: + name: + type: string + valueFrom: + type: string + type: object + type: array + type: object + namespace: + type: string + services: + items: + description: |- + The Service Connect service object configuration. For more information, see + Service Connect (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html) + in the Amazon Elastic Container Service Developer Guide. + properties: + clientAliases: + items: + description: |- + Each alias ("endpoint") is a fully-qualified name and port number that other + tasks ("clients") can use to connect to this service. + + + Each name and port mapping must be unique within the namespace. + + + Tasks that run in a namespace can use short names to connect to services + in the namespace. Tasks can connect to services across all of the clusters + in the namespace. Tasks connect through a managed proxy container that collects + logs and metrics for increased visibility. Only the tasks that Amazon ECS + services create are supported with Service Connect. For more information, + see Service Connect (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html) + in the Amazon Elastic Container Service Developer Guide. + properties: + dnsName: + type: string + port: + format: int64 + type: integer + type: object + type: array + discoveryName: + type: string + ingressPortOverride: + format: int64 + type: integer + portName: + type: string + timeout: + description: |- + An object that represents the timeout configurations for Service Connect. + + + If idleTimeout is set to a time that is less than perRequestTimeout, the + connection will close when the idleTimeout is reached and not the perRequestTimeout. + properties: + idleTimeoutSeconds: + format: int64 + type: integer + perRequestTimeoutSeconds: + format: int64 + type: integer + type: object + tls: + description: An object that represents the configuration + for Service Connect TLS. + properties: + issuerCertificateAuthority: + description: |- + An object that represents the Amazon Web Services Private Certificate Authority + certificate. + properties: + awsPCAAuthorityARN: + type: string + type: object + kmsKey: + type: string + roleARN: + type: string + type: object + type: object + type: array + type: object + serviceRegistries: + description: |- + The details of the service discovery registry to associate with this service. + For more information, see Service discovery (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-discovery.html). + + + Each service may be associated with one service registry. Multiple service + registries for each service isn't supported. + items: + description: |- + The details for the service registry. + + + Each service may be associated with one service registry. Multiple service + registries for each service are not supported. + + + When you add, update, or remove the service registries configuration, Amazon + ECS starts a new deployment. New tasks are registered and deregistered to + the updated service registry configuration. + properties: + containerName: + type: string + containerPort: + format: int64 + type: integer + port: + format: int64 + type: integer + registryARN: + type: string + type: object + type: array + tags: + description: |- + The metadata that you apply to the service to help you categorize and organize + them. Each tag consists of a key and an optional value, both of which you + define. When a service is deleted, the tags are deleted as well. + + + The following basic restrictions apply to tags: + + + * Maximum number of tags per resource - 50 + + + * For each resource, each tag key must be unique, and each tag key can + have only one value. + + + * Maximum key length - 128 Unicode characters in UTF-8 + + + * Maximum value length - 256 Unicode characters in UTF-8 + + + * If your tagging schema is used across multiple services and resources, + remember that other services may have restrictions on allowed characters. + Generally allowed characters are: letters, numbers, and spaces representable + in UTF-8, and the following characters: + - = . _ : / @. + + + * Tag keys and values are case-sensitive. + + + * Do not use aws:, AWS:, or any upper or lowercase combination of such + as a prefix for either keys or values as it is reserved for Amazon Web + Services use. You cannot edit or delete tag keys or values with this prefix. + Tags with this prefix do not count against your tags per resource limit. + items: + description: |- + The metadata that you apply to a resource to help you categorize and organize + them. Each tag consists of a key and an optional value. You define them. + + + The following basic restrictions apply to tags: + + + * Maximum number of tags per resource - 50 + + + * For each resource, each tag key must be unique, and each tag key can + have only one value. + + + * Maximum key length - 128 Unicode characters in UTF-8 + + + * Maximum value length - 256 Unicode characters in UTF-8 + + + * If your tagging schema is used across multiple services and resources, + remember that other services may have restrictions on allowed characters. + Generally allowed characters are: letters, numbers, and spaces representable + in UTF-8, and the following characters: + - = . _ : / @. + + + * Tag keys and values are case-sensitive. + + + * Do not use aws:, AWS:, or any upper or lowercase combination of such + as a prefix for either keys or values as it is reserved for Amazon Web + Services use. You cannot edit or delete tag keys or values with this prefix. + Tags with this prefix do not count against your tags per resource limit. + properties: + key: + type: string + value: + type: string + type: object + type: array + taskDefinition: + description: |- + The family and revision (family:revision) or full ARN of the task definition + to run in your service. If a revision isn't specified, the latest ACTIVE + revision is used. + + + A task definition must be specified if the service uses either the ECS or + CODE_DEPLOY deployment controllers. + + + For more information about deployment types, see Amazon ECS deployment types + (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html). + type: string + taskDefinitionRef: + description: "AWSResourceReferenceWrapper provides a wrapper around + *AWSResourceReference\ntype to provide more user friendly syntax + for references using 'from' field\nEx:\nAPIIDRef:\n\n\n\tfrom:\n\t + \ name: my-api" + properties: + from: + description: |- + AWSResourceReference provides all the values necessary to reference another + k8s resource for finding the identifier(Id/ARN/Name) + properties: + name: + type: string + namespace: + type: string + type: object + type: object + volumeConfigurations: + description: |- + The configuration for a volume specified in the task definition as a volume + that is configured at launch time. Currently, the only supported volume type + is an Amazon EBS volume. + items: + description: |- + The configuration for a volume specified in the task definition as a volume + that is configured at launch time. Currently, the only supported volume type + is an Amazon EBS volume. + properties: + managedEBSVolume: + description: |- + The configuration for the Amazon EBS volume that Amazon ECS creates and manages + on your behalf. These settings are used to create each Amazon EBS volume, + with one volume created for each task in the service. + + + Many of these parameters map 1:1 with the Amazon EBS CreateVolume API request + parameters. + properties: + encrypted: + type: boolean + filesystemType: + type: string + iops: + format: int64 + type: integer + kmsKeyID: + type: string + roleARN: + type: string + sizeInGiB: + format: int64 + type: integer + snapshotID: + type: string + tagSpecifications: + items: + description: The tag specifications of an Amazon EBS volume. + properties: + propagateTags: + type: string + resourceType: + type: string + tags: + items: + description: |- + The metadata that you apply to a resource to help you categorize and organize + them. Each tag consists of a key and an optional value. You define them. + + + The following basic restrictions apply to tags: + + + * Maximum number of tags per resource - 50 + + + * For each resource, each tag key must be unique, and each tag key can + have only one value. + + + * Maximum key length - 128 Unicode characters in UTF-8 + + + * Maximum value length - 256 Unicode characters in UTF-8 + + + * If your tagging schema is used across multiple services and resources, + remember that other services may have restrictions on allowed characters. + Generally allowed characters are: letters, numbers, and spaces representable + in UTF-8, and the following characters: + - = . _ : / @. + + + * Tag keys and values are case-sensitive. + + + * Do not use aws:, AWS:, or any upper or lowercase combination of such + as a prefix for either keys or values as it is reserved for Amazon Web + Services use. You cannot edit or delete tag keys or values with this prefix. + Tags with this prefix do not count against your tags per resource limit. + properties: + key: + type: string + value: + type: string + type: object + type: array + type: object + type: array + throughput: + format: int64 + type: integer + volumeType: + type: string + type: object + name: + type: string + type: object + type: array + required: + - name + type: object + status: + description: ServiceStatus defines the observed state of Service + properties: + ackResourceMetadata: + description: |- + All CRs managed by ACK have a common `Status.ACKResourceMetadata` member + that is used to contain resource sync state, account ownership, + constructed ARN for the resource + properties: + arn: + description: |- + ARN is the Amazon Resource Name for the resource. This is a + globally-unique identifier and is set only by the ACK service controller + once the controller has orchestrated the creation of the resource OR + when it has verified that an "adopted" resource (a resource where the + ARN annotation was set by the Kubernetes user on the CR) exists and + matches the supplied CR's Spec field values. + TODO(vijat@): Find a better strategy for resources that do not have ARN in CreateOutputResponse + https://github.com/aws/aws-controllers-k8s/issues/270 + type: string + ownerAccountID: + description: |- + OwnerAccountID is the AWS Account ID of the account that owns the + backend AWS service API resource. + type: string + region: + description: Region is the AWS region in which the resource exists + or will exist. + type: string + required: + - ownerAccountID + - region + type: object + clusterARN: + description: The Amazon Resource Name (ARN) of the cluster that hosts + the service. + type: string + conditions: + description: |- + All CRS managed by ACK have a common `Status.Conditions` member that + contains a collection of `ackv1alpha1.Condition` objects that describe + the various terminal states of the CR and its backend AWS service API + resource + items: + description: |- + Condition is the common struct used by all CRDs managed by ACK service + controllers to indicate terminal states of the CR and its backend AWS + service API resource + properties: + lastTransitionTime: + description: Last time the condition transitioned from one status + to another. + format: date-time + type: string + message: + description: A human readable message indicating details about + the transition. + type: string + reason: + description: The reason for the condition's last transition. + type: string + status: + description: Status of the condition, one of True, False, Unknown. + type: string + type: + description: Type is the type of the Condition + type: string + required: + - status + - type + type: object + type: array + createdAt: + description: The Unix timestamp for the time when the service was + created. + format: date-time + type: string + createdBy: + description: The principal that created the service. + type: string + deployments: + description: The current state of deployments for the service. + items: + description: |- + The details of an Amazon ECS service deployment. This is used only when a + service uses the ECS deployment controller type. + properties: + capacityProviderStrategy: + items: + description: |- + The details of a capacity provider strategy. A capacity provider strategy + can be set when using the RunTask or CreateCluster APIs or as the default + capacity provider strategy for a cluster with the CreateCluster API. + + + Only capacity providers that are already associated with a cluster and have + an ACTIVE or UPDATING status can be used in a capacity provider strategy. + The PutClusterCapacityProviders API is used to associate a capacity provider + with a cluster. + + + If specifying a capacity provider that uses an Auto Scaling group, the capacity + provider must already be created. New Auto Scaling group capacity providers + can be created with the CreateCapacityProvider API operation. + + + To use a Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT + capacity providers. The Fargate capacity providers are available to all accounts + and only need to be associated with a cluster to be used in a capacity provider + strategy. + + + A capacity provider strategy may contain a maximum of 6 capacity providers. + properties: + base: + format: int64 + type: integer + capacityProvider: + type: string + weight: + format: int64 + type: integer + type: object + type: array + createdAt: + format: date-time + type: string + desiredCount: + format: int64 + type: integer + failedTasks: + format: int64 + type: integer + id: + type: string + launchType: + type: string + networkConfiguration: + description: The network configuration for a task or service. + properties: + awsVPCConfiguration: + description: |- + An object representing the networking details for a task or service. For + example awsvpcConfiguration={subnets=["subnet-12344321"],securityGroups=["sg-12344321"]} + properties: + assignPublicIP: + type: string + securityGroups: + items: + type: string + type: array + subnets: + items: + type: string + type: array + type: object + type: object + pendingCount: + format: int64 + type: integer + platformFamily: + type: string + platformVersion: + type: string + rolloutState: + type: string + rolloutStateReason: + type: string + runningCount: + format: int64 + type: integer + serviceConnectConfiguration: + description: |- + The Service Connect configuration of your Amazon ECS service. The configuration + for this service to discover and connect to services, and be discovered by, + and connected from, other services within a namespace. + + + Tasks that run in a namespace can use short names to connect to services + in the namespace. Tasks can connect to services across all of the clusters + in the namespace. Tasks connect through a managed proxy container that collects + logs and metrics for increased visibility. Only the tasks that Amazon ECS + services create are supported with Service Connect. For more information, + see Service Connect (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html) + in the Amazon Elastic Container Service Developer Guide. + properties: + enabled: + type: boolean + logConfiguration: + description: |- + The log configuration for the container. This parameter maps to LogConfig + in the Create a container (https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate) + section of the Docker Remote API (https://docs.docker.com/engine/api/v1.35/) + and the --log-driver option to docker run (https://docs.docker.com/engine/reference/commandline/run/). + + + By default, containers use the same logging driver that the Docker daemon + uses. However, the container might use a different logging driver than the + Docker daemon by specifying a log driver configuration in the container definition. + For more information about the options for different supported log drivers, + see Configure logging drivers (https://docs.docker.com/engine/admin/logging/overview/) + in the Docker documentation. + + + Understand the following when specifying a log configuration for your containers. + + + * Amazon ECS currently supports a subset of the logging drivers available + to the Docker daemon. Additional log drivers may be available in future + releases of the Amazon ECS container agent. For tasks on Fargate, the + supported log drivers are awslogs, splunk, and awsfirelens. For tasks + hosted on Amazon EC2 instances, the supported log drivers are awslogs, + fluentd, gelf, json-file, journald, logentries,syslog, splunk, and awsfirelens. + + + * This parameter requires version 1.18 of the Docker Remote API or greater + on your container instance. + + + * For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container + agent must register the available logging drivers with the ECS_AVAILABLE_LOGGING_DRIVERS + environment variable before containers placed on that instance can use + these log configuration options. For more information, see Amazon ECS + container agent configuration (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html) + in the Amazon Elastic Container Service Developer Guide. + + + * For tasks that are on Fargate, because you don't have access to the + underlying infrastructure your tasks are hosted on, any additional software + needed must be installed outside of the task. For example, the Fluentd + output aggregators or a remote host running Logstash to send Gelf logs + to. + properties: + logDriver: + type: string + options: + additionalProperties: + type: string + type: object + secretOptions: + items: + description: |- + An object representing the secret to expose to your container. Secrets can + be exposed to a container in the following ways: + + + * To inject sensitive data into your containers as environment variables, + use the secrets container definition parameter. + + + * To reference sensitive information in the log configuration of a container, + use the secretOptions container definition parameter. + + + For more information, see Specifying sensitive data (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/specifying-sensitive-data.html) + in the Amazon Elastic Container Service Developer Guide. + properties: + name: + type: string + valueFrom: + type: string + type: object + type: array + type: object + namespace: + type: string + services: + items: + description: |- + The Service Connect service object configuration. For more information, see + Service Connect (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html) + in the Amazon Elastic Container Service Developer Guide. + properties: + clientAliases: + items: + description: |- + Each alias ("endpoint") is a fully-qualified name and port number that other + tasks ("clients") can use to connect to this service. + + + Each name and port mapping must be unique within the namespace. + + + Tasks that run in a namespace can use short names to connect to services + in the namespace. Tasks can connect to services across all of the clusters + in the namespace. Tasks connect through a managed proxy container that collects + logs and metrics for increased visibility. Only the tasks that Amazon ECS + services create are supported with Service Connect. For more information, + see Service Connect (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html) + in the Amazon Elastic Container Service Developer Guide. + properties: + dnsName: + type: string + port: + format: int64 + type: integer + type: object + type: array + discoveryName: + type: string + ingressPortOverride: + format: int64 + type: integer + portName: + type: string + timeout: + description: |- + An object that represents the timeout configurations for Service Connect. + + + If idleTimeout is set to a time that is less than perRequestTimeout, the + connection will close when the idleTimeout is reached and not the perRequestTimeout. + properties: + idleTimeoutSeconds: + format: int64 + type: integer + perRequestTimeoutSeconds: + format: int64 + type: integer + type: object + tls: + description: An object that represents the configuration + for Service Connect TLS. + properties: + issuerCertificateAuthority: + description: |- + An object that represents the Amazon Web Services Private Certificate Authority + certificate. + properties: + awsPCAAuthorityARN: + type: string + type: object + kmsKey: + type: string + roleARN: + type: string + type: object + type: object + type: array + type: object + serviceConnectResources: + items: + description: |- + The Service Connect resource. Each configuration maps a discovery name to + a Cloud Map service name. The data is stored in Cloud Map as part of the + Service Connect configuration for each discovery name of this Amazon ECS + service. + + + A task can resolve the dnsName for each of the clientAliases of a service. + However a task can't resolve the discovery names. If you want to connect + to a service, refer to the ServiceConnectConfiguration of that service for + the list of clientAliases that you can use. + properties: + discoveryARN: + type: string + discoveryName: + type: string + type: object + type: array + status: + type: string + taskDefinition: + type: string + updatedAt: + format: date-time + type: string + volumeConfigurations: + items: + description: |- + The configuration for a volume specified in the task definition as a volume + that is configured at launch time. Currently, the only supported volume type + is an Amazon EBS volume. + properties: + managedEBSVolume: + description: |- + The configuration for the Amazon EBS volume that Amazon ECS creates and manages + on your behalf. These settings are used to create each Amazon EBS volume, + with one volume created for each task in the service. + + + Many of these parameters map 1:1 with the Amazon EBS CreateVolume API request + parameters. + properties: + encrypted: + type: boolean + filesystemType: + type: string + iops: + format: int64 + type: integer + kmsKeyID: + type: string + roleARN: + type: string + sizeInGiB: + format: int64 + type: integer + snapshotID: + type: string + tagSpecifications: + items: + description: The tag specifications of an Amazon + EBS volume. + properties: + propagateTags: + type: string + resourceType: + type: string + tags: + items: + description: |- + The metadata that you apply to a resource to help you categorize and organize + them. Each tag consists of a key and an optional value. You define them. + + + The following basic restrictions apply to tags: + + + * Maximum number of tags per resource - 50 + + + * For each resource, each tag key must be unique, and each tag key can + have only one value. + + + * Maximum key length - 128 Unicode characters in UTF-8 + + + * Maximum value length - 256 Unicode characters in UTF-8 + + + * If your tagging schema is used across multiple services and resources, + remember that other services may have restrictions on allowed characters. + Generally allowed characters are: letters, numbers, and spaces representable + in UTF-8, and the following characters: + - = . _ : / @. + + + * Tag keys and values are case-sensitive. + + + * Do not use aws:, AWS:, or any upper or lowercase combination of such + as a prefix for either keys or values as it is reserved for Amazon Web + Services use. You cannot edit or delete tag keys or values with this prefix. + Tags with this prefix do not count against your tags per resource limit. + properties: + key: + type: string + value: + type: string + type: object + type: array + type: object + type: array + throughput: + format: int64 + type: integer + volumeType: + type: string + type: object + name: + type: string + type: object + type: array + type: object + type: array + events: + description: |- + The event stream for your service. A maximum of 100 of the latest events + are displayed. + items: + description: The details for an event that's associated with a service. + properties: + createdAt: + format: date-time + type: string + id: + type: string + message: + type: string + type: object + type: array + pendingCount: + description: The number of tasks in the cluster that are in the PENDING + state. + format: int64 + type: integer + platformFamily: + description: |- + The operating system that your tasks in the service run on. A platform family + is specified only for tasks using the Fargate launch type. + + + All tasks that run as part of this service must use the same platformFamily + value as the service (for example, LINUX). + type: string + roleARN: + description: |- + The ARN of the IAM role that's associated with the service. It allows the + Amazon ECS container agent to register container instances with an Elastic + Load Balancing load balancer. + type: string + runningCount: + description: The number of tasks in the cluster that are in the RUNNING + state. + format: int64 + type: integer + status: + description: The status of the service. The valid values are ACTIVE, + DRAINING, or INACTIVE. + type: string + taskSets: + description: |- + Information about a set of Amazon ECS tasks in either an CodeDeploy or an + EXTERNAL deployment. An Amazon ECS task set includes details such as the + desired number of tasks, how many tasks are running, and whether the task + set serves production traffic. + items: + description: |- + Information about a set of Amazon ECS tasks in either an CodeDeploy or an + EXTERNAL deployment. An Amazon ECS task set includes details such as the + desired number of tasks, how many tasks are running, and whether the task + set serves production traffic. + properties: + capacityProviderStrategy: + items: + description: |- + The details of a capacity provider strategy. A capacity provider strategy + can be set when using the RunTask or CreateCluster APIs or as the default + capacity provider strategy for a cluster with the CreateCluster API. + + + Only capacity providers that are already associated with a cluster and have + an ACTIVE or UPDATING status can be used in a capacity provider strategy. + The PutClusterCapacityProviders API is used to associate a capacity provider + with a cluster. + + + If specifying a capacity provider that uses an Auto Scaling group, the capacity + provider must already be created. New Auto Scaling group capacity providers + can be created with the CreateCapacityProvider API operation. + + + To use a Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT + capacity providers. The Fargate capacity providers are available to all accounts + and only need to be associated with a cluster to be used in a capacity provider + strategy. + + + A capacity provider strategy may contain a maximum of 6 capacity providers. + properties: + base: + format: int64 + type: integer + capacityProvider: + type: string + weight: + format: int64 + type: integer + type: object + type: array + clusterARN: + type: string + computedDesiredCount: + format: int64 + type: integer + createdAt: + format: date-time + type: string + externalID: + type: string + id: + type: string + launchType: + type: string + loadBalancers: + items: + description: |- + The load balancer configuration to use with a service or task set. + + + When you add, update, or remove a load balancer configuration, Amazon ECS + starts a new deployment with the updated Elastic Load Balancing configuration. + This causes tasks to register to and deregister from load balancers. + + + We recommend that you verify this on a test environment before you update + the Elastic Load Balancing configuration. + + + A service-linked role is required for services that use multiple target groups. + For more information, see Using service-linked roles (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html) + in the Amazon Elastic Container Service Developer Guide. + properties: + containerName: + type: string + containerPort: + format: int64 + type: integer + loadBalancerName: + type: string + targetGroupARN: + type: string + type: object + type: array + networkConfiguration: + description: The network configuration for a task or service. + properties: + awsVPCConfiguration: + description: |- + An object representing the networking details for a task or service. For + example awsvpcConfiguration={subnets=["subnet-12344321"],securityGroups=["sg-12344321"]} + properties: + assignPublicIP: + type: string + securityGroups: + items: + type: string + type: array + subnets: + items: + type: string + type: array + type: object + type: object + pendingCount: + format: int64 + type: integer + platformFamily: + type: string + platformVersion: + type: string + runningCount: + format: int64 + type: integer + scale: + description: |- + A floating-point percentage of the desired number of tasks to place and keep + running in the task set. + properties: + unit: + type: string + value: + type: number + type: object + serviceARN: + type: string + serviceRegistries: + items: + description: |- + The details for the service registry. + + + Each service may be associated with one service registry. Multiple service + registries for each service are not supported. + + + When you add, update, or remove the service registries configuration, Amazon + ECS starts a new deployment. New tasks are registered and deregistered to + the updated service registry configuration. + properties: + containerName: + type: string + containerPort: + format: int64 + type: integer + port: + format: int64 + type: integer + registryARN: + type: string + type: object + type: array + stabilityStatus: + type: string + stabilityStatusAt: + format: date-time + type: string + startedBy: + type: string + status: + type: string + tags: + items: + description: |- + The metadata that you apply to a resource to help you categorize and organize + them. Each tag consists of a key and an optional value. You define them. + + + The following basic restrictions apply to tags: + + + * Maximum number of tags per resource - 50 + + + * For each resource, each tag key must be unique, and each tag key can + have only one value. + + + * Maximum key length - 128 Unicode characters in UTF-8 + + + * Maximum value length - 256 Unicode characters in UTF-8 + + + * If your tagging schema is used across multiple services and resources, + remember that other services may have restrictions on allowed characters. + Generally allowed characters are: letters, numbers, and spaces representable + in UTF-8, and the following characters: + - = . _ : / @. + + + * Tag keys and values are case-sensitive. + + + * Do not use aws:, AWS:, or any upper or lowercase combination of such + as a prefix for either keys or values as it is reserved for Amazon Web + Services use. You cannot edit or delete tag keys or values with this prefix. + Tags with this prefix do not count against your tags per resource limit. + properties: + key: + type: string + value: + type: string + type: object + type: array + taskDefinition: + type: string + taskSetARN: + type: string + updatedAt: + format: date-time + type: string + type: object + type: array + type: object + type: object + served: true + storage: true + subresources: + status: {} +status: + acceptedNames: + kind: "" + plural: "" + conditions: null + storedVersions: null diff --git a/operators/ack-ecs-controller/0.0.8/manifests/ecs.services.k8s.aws_taskdefinitions.yaml b/operators/ack-ecs-controller/0.0.8/manifests/ecs.services.k8s.aws_taskdefinitions.yaml new file mode 100644 index 00000000000..1cf85bf217d --- /dev/null +++ b/operators/ack-ecs-controller/0.0.8/manifests/ecs.services.k8s.aws_taskdefinitions.yaml @@ -0,0 +1,1450 @@ +apiVersion: apiextensions.k8s.io/v1 +kind: CustomResourceDefinition +metadata: + annotations: + controller-gen.kubebuilder.io/version: v0.14.0 + creationTimestamp: null + name: taskdefinitions.ecs.services.k8s.aws +spec: + group: ecs.services.k8s.aws + names: + kind: TaskDefinition + listKind: TaskDefinitionList + plural: taskdefinitions + singular: taskdefinition + scope: Namespaced + versions: + - additionalPrinterColumns: + - jsonPath: .spec.family + name: FAMILY + type: string + - jsonPath: .spec.cpu + name: CPU + type: string + - jsonPath: .spec.memory + name: MEMORY + type: string + - jsonPath: .spec.networkMode + name: NETWORKMODE + type: string + - jsonPath: .status.conditions[?(@.type=="ACK.ResourceSynced")].status + name: Synced + type: string + name: v1alpha1 + schema: + openAPIV3Schema: + description: TaskDefinition is the Schema for the TaskDefinitions API + properties: + apiVersion: + description: |- + APIVersion defines the versioned schema of this representation of an object. + Servers should convert recognized schemas to the latest internal value, and + may reject unrecognized values. + More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources + type: string + kind: + description: |- + Kind is a string value representing the REST resource this object represents. + Servers may infer this from the endpoint the client submits requests to. + Cannot be updated. + In CamelCase. + More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds + type: string + metadata: + type: object + spec: + description: |- + TaskDefinitionSpec defines the desired state of TaskDefinition. + + + The details of a task definition which describes the container and volume + definitions of an Amazon Elastic Container Service task. You can specify + which Docker images to use, the required resources, and other configurations + related to launching the task definition through an Amazon ECS service or + task. + properties: + containerDefinitions: + description: |- + A list of container definitions in JSON format that describe the different + containers that make up your task. + items: + description: |- + Container definitions are used in task definitions to describe the different + containers that are launched as part of a task. + properties: + command: + items: + type: string + type: array + cpu: + format: int64 + type: integer + credentialSpecs: + items: + type: string + type: array + dependsOn: + items: + description: |- + The dependencies defined for container startup and shutdown. A container + can contain multiple dependencies. When a dependency is defined for container + startup, for container shutdown it is reversed. + + + Your Amazon ECS container instances require at least version 1.26.0 of the + container agent to use container dependencies. However, we recommend using + the latest container agent version. For information about checking your agent + version and updating to the latest version, see Updating the Amazon ECS Container + Agent (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-update.html) + in the Amazon Elastic Container Service Developer Guide. If you're using + an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 + of the ecs-init package. If your container instances are launched from version + 20190301 or later, then they contain the required versions of the container + agent and ecs-init. For more information, see Amazon ECS-optimized Linux + AMI (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html) + in the Amazon Elastic Container Service Developer Guide. + + + For tasks that use the Fargate launch type, the task or service requires + the following platforms: + + + * Linux platform version 1.3.0 or later. + + + * Windows platform version 1.0.0 or later. + + + For more information about how to create a container dependency, see Container + dependency (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/example_task_definitions.html#example_task_definition-containerdependency) + in the Amazon Elastic Container Service Developer Guide. + properties: + condition: + type: string + containerName: + type: string + type: object + type: array + disableNetworking: + type: boolean + dnsSearchDomains: + items: + type: string + type: array + dnsServers: + items: + type: string + type: array + dockerLabels: + additionalProperties: + type: string + type: object + dockerSecurityOptions: + items: + type: string + type: array + entryPoint: + items: + type: string + type: array + environment: + items: + description: A key-value pair object. + properties: + name: + type: string + value: + type: string + type: object + type: array + environmentFiles: + items: + description: |- + A list of files containing the environment variables to pass to a container. + You can specify up to ten environment files. The file must have a .env file + extension. Each line in an environment file should contain an environment + variable in VARIABLE=VALUE format. Lines beginning with # are treated as + comments and are ignored. + + + If there are environment variables specified using the environment parameter + in a container definition, they take precedence over the variables contained + within an environment file. If multiple environment files are specified that + contain the same variable, they're processed from the top down. We recommend + that you use unique variable names. For more information, see Specifying + environment variables (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/taskdef-envfiles.html) + in the Amazon Elastic Container Service Developer Guide. + + + You must use the following platforms for the Fargate launch type: + + + * Linux platform version 1.4.0 or later. + + + * Windows platform version 1.0.0 or later. + + + Consider the following when using the Fargate launch type: + + + * The file is handled like a native Docker env-file. + + + * There is no support for shell escape handling. + + + * The container entry point interperts the VARIABLE values. + properties: + type: + type: string + value: + type: string + type: object + type: array + essential: + type: boolean + extraHosts: + items: + description: |- + Hostnames and IP address entries that are added to the /etc/hosts file of + a container via the extraHosts parameter of its ContainerDefinition. + properties: + hostname: + type: string + ipAddress: + type: string + type: object + type: array + firelensConfiguration: + description: |- + The FireLens configuration for the container. This is used to specify and + configure a log router for container logs. For more information, see Custom + log routing (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_firelens.html) + in the Amazon Elastic Container Service Developer Guide. + properties: + options: + additionalProperties: + type: string + type: object + type: + type: string + type: object + healthCheck: + description: |- + An object representing a container health check. Health check parameters + that are specified in a container definition override any Docker health checks + that exist in the container image (such as those specified in a parent image + or from the image's Dockerfile). This configuration maps to the HEALTHCHECK + parameter of docker run (https://docs.docker.com/engine/reference/run/). + + + The Amazon ECS container agent only monitors and reports on the health checks + specified in the task definition. Amazon ECS does not monitor Docker health + checks that are embedded in a container image and not specified in the container + definition. Health check parameters that are specified in a container definition + override any Docker health checks that exist in the container image. + + + You can view the health status of both individual containers and a task with + the DescribeTasks API operation or when viewing the task details in the console. + + + The health check is designed to make sure that your containers survive agent + restarts, upgrades, or temporary unavailability. + + + The following describes the possible healthStatus values for a container: + + + * HEALTHY-The container health check has passed successfully. + + + * UNHEALTHY-The container health check has failed. + + + * UNKNOWN-The container health check is being evaluated, there's no container + health check defined, or Amazon ECS doesn't have the health status of + the container. + + + The following describes the possible healthStatus values based on the container + health checker status of essential containers in the task with the following + priority order (high to low): + + + * UNHEALTHY-One or more essential containers have failed their health + check. + + + * UNKNOWN-Any essential container running within the task is in an UNKNOWN + state and no other essential containers have an UNHEALTHY state. + + + * HEALTHY-All essential containers within the task have passed their health + checks. + + + Consider the following task health example with 2 containers. + + + * If Container1 is UNHEALTHY and Container2 is UNKNOWN, the task health + is UNHEALTHY. + + + * If Container1 is UNHEALTHY and Container2 is HEALTHY, the task health + is UNHEALTHY. + + + * If Container1 is HEALTHY and Container2 is UNKNOWN, the task health + is UNKNOWN. + + + * If Container1 is HEALTHY and Container2 is HEALTHY, the task health + is HEALTHY. + + + Consider the following task health example with 3 containers. + + + * If Container1 is UNHEALTHY and Container2 is UNKNOWN, and Container3 + is UNKNOWN, the task health is UNHEALTHY. + + + * If Container1 is UNHEALTHY and Container2 is UNKNOWN, and Container3 + is HEALTHY, the task health is UNHEALTHY. + + + * If Container1 is UNHEALTHY and Container2 is HEALTHY, and Container3 + is HEALTHY, the task health is UNHEALTHY. + + + * If Container1 is HEALTHY and Container2 is UNKNOWN, and Container3 is + HEALTHY, the task health is UNKNOWN. + + + * If Container1 is HEALTHY and Container2 is UNKNOWN, and Container3 is + UNKNOWN, the task health is UNKNOWN. + + + * If Container1 is HEALTHY and Container2 is HEALTHY, and Container3 is + HEALTHY, the task health is HEALTHY. + + + If a task is run manually, and not as part of a service, the task will continue + its lifecycle regardless of its health status. For tasks that are part of + a service, if the task reports as unhealthy then the task will be stopped + and the service scheduler will replace it. + + + The following are notes about container health check support: + + + * When the Amazon ECS agent cannot connect to the Amazon ECS service, + the service reports the container as UNHEALTHY. + + + * The health check statuses are the "last heard from" response from the + Amazon ECS agent. There are no assumptions made about the status of the + container health checks. + + + * Container health checks require version 1.17.0 or greater of the Amazon + ECS container agent. For more information, see Updating the Amazon ECS + container agent (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-update.html). + + + * Container health checks are supported for Fargate tasks if you're using + platform version 1.1.0 or greater. For more information, see Fargate platform + versions (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html). + + + * Container health checks aren't supported for tasks that are part of + a service that's configured to use a Classic Load Balancer. + properties: + command: + items: + type: string + type: array + interval: + format: int64 + type: integer + retries: + format: int64 + type: integer + startPeriod: + format: int64 + type: integer + timeout: + format: int64 + type: integer + type: object + hostname: + type: string + image: + type: string + interactive: + type: boolean + links: + items: + type: string + type: array + linuxParameters: + description: |- + The Linux-specific options that are applied to the container, such as Linux + KernelCapabilities (https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_KernelCapabilities.html). + properties: + capabilities: + description: |- + The Linux capabilities for the container that are added to or dropped from + the default configuration provided by Docker. For more information about + the default capabilities and the non-default available capabilities, see + Runtime privilege and Linux capabilities (https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities) + in the Docker run reference. For more detailed information about these Linux + capabilities, see the capabilities(7) (http://man7.org/linux/man-pages/man7/capabilities.7.html) + Linux manual page. + properties: + add: + items: + type: string + type: array + drop: + items: + type: string + type: array + type: object + devices: + items: + description: An object representing a container instance + host device. + properties: + containerPath: + type: string + hostPath: + type: string + permissions: + items: + type: string + type: array + type: object + type: array + initProcessEnabled: + type: boolean + maxSwap: + format: int64 + type: integer + sharedMemorySize: + format: int64 + type: integer + swappiness: + format: int64 + type: integer + tmpfs: + items: + description: The container path, mount options, and size + of the tmpfs mount. + properties: + containerPath: + type: string + mountOptions: + items: + type: string + type: array + size: + format: int64 + type: integer + type: object + type: array + type: object + logConfiguration: + description: |- + The log configuration for the container. This parameter maps to LogConfig + in the Create a container (https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate) + section of the Docker Remote API (https://docs.docker.com/engine/api/v1.35/) + and the --log-driver option to docker run (https://docs.docker.com/engine/reference/commandline/run/). + + + By default, containers use the same logging driver that the Docker daemon + uses. However, the container might use a different logging driver than the + Docker daemon by specifying a log driver configuration in the container definition. + For more information about the options for different supported log drivers, + see Configure logging drivers (https://docs.docker.com/engine/admin/logging/overview/) + in the Docker documentation. + + + Understand the following when specifying a log configuration for your containers. + + + * Amazon ECS currently supports a subset of the logging drivers available + to the Docker daemon. Additional log drivers may be available in future + releases of the Amazon ECS container agent. For tasks on Fargate, the + supported log drivers are awslogs, splunk, and awsfirelens. For tasks + hosted on Amazon EC2 instances, the supported log drivers are awslogs, + fluentd, gelf, json-file, journald, logentries,syslog, splunk, and awsfirelens. + + + * This parameter requires version 1.18 of the Docker Remote API or greater + on your container instance. + + + * For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container + agent must register the available logging drivers with the ECS_AVAILABLE_LOGGING_DRIVERS + environment variable before containers placed on that instance can use + these log configuration options. For more information, see Amazon ECS + container agent configuration (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html) + in the Amazon Elastic Container Service Developer Guide. + + + * For tasks that are on Fargate, because you don't have access to the + underlying infrastructure your tasks are hosted on, any additional software + needed must be installed outside of the task. For example, the Fluentd + output aggregators or a remote host running Logstash to send Gelf logs + to. + properties: + logDriver: + type: string + options: + additionalProperties: + type: string + type: object + secretOptions: + items: + description: |- + An object representing the secret to expose to your container. Secrets can + be exposed to a container in the following ways: + + + * To inject sensitive data into your containers as environment variables, + use the secrets container definition parameter. + + + * To reference sensitive information in the log configuration of a container, + use the secretOptions container definition parameter. + + + For more information, see Specifying sensitive data (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/specifying-sensitive-data.html) + in the Amazon Elastic Container Service Developer Guide. + properties: + name: + type: string + valueFrom: + type: string + type: object + type: array + type: object + memory: + format: int64 + type: integer + memoryReservation: + format: int64 + type: integer + mountPoints: + items: + description: The details for a volume mount point that's used + in a container definition. + properties: + containerPath: + type: string + readOnly: + type: boolean + sourceVolume: + type: string + type: object + type: array + name: + type: string + portMappings: + items: + description: |- + Port mappings allow containers to access ports on the host container instance + to send or receive traffic. Port mappings are specified as part of the container + definition. + + + If you use containers in a task with the awsvpc or host network mode, specify + the exposed ports using containerPort. The hostPort can be left blank or + it must be the same value as the containerPort. + + + Most fields of this parameter (containerPort, hostPort, protocol) maps to + PortBindings in the Create a container (https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate) + section of the Docker Remote API (https://docs.docker.com/engine/api/v1.35/) + and the --publish option to docker run (https://docs.docker.com/engine/reference/commandline/run/). + If the network mode of a task definition is set to host, host ports must + either be undefined or match the container port in the port mapping. + + + You can't expose the same container port for multiple protocols. If you attempt + this, an error is returned. + + + After a task reaches the RUNNING status, manual and automatic host and container + port assignments are visible in the networkBindings section of DescribeTasks + API responses. + properties: + appProtocol: + type: string + containerPort: + format: int64 + type: integer + containerPortRange: + type: string + hostPort: + format: int64 + type: integer + name: + type: string + protocol: + type: string + type: object + type: array + privileged: + type: boolean + pseudoTerminal: + type: boolean + readonlyRootFilesystem: + type: boolean + repositoryCredentials: + description: The repository credentials for private registry + authentication. + properties: + credentialsParameter: + type: string + type: object + resourceRequirements: + items: + description: |- + The type and amount of a resource to assign to a container. The supported + resource types are GPUs and Elastic Inference accelerators. For more information, + see Working with GPUs on Amazon ECS (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-gpu.html) + or Working with Amazon Elastic Inference on Amazon ECS (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-inference.html) + in the Amazon Elastic Container Service Developer Guide + properties: + type: + type: string + value: + type: string + type: object + type: array + secrets: + items: + description: |- + An object representing the secret to expose to your container. Secrets can + be exposed to a container in the following ways: + + + * To inject sensitive data into your containers as environment variables, + use the secrets container definition parameter. + + + * To reference sensitive information in the log configuration of a container, + use the secretOptions container definition parameter. + + + For more information, see Specifying sensitive data (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/specifying-sensitive-data.html) + in the Amazon Elastic Container Service Developer Guide. + properties: + name: + type: string + valueFrom: + type: string + type: object + type: array + startTimeout: + format: int64 + type: integer + stopTimeout: + format: int64 + type: integer + systemControls: + items: + description: |- + A list of namespaced kernel parameters to set in the container. This parameter + maps to Sysctls in the Create a container (https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate) + section of the Docker Remote API (https://docs.docker.com/engine/api/v1.35/) + and the --sysctl option to docker run (https://docs.docker.com/engine/reference/run/#security-configuration). + For example, you can configure net.ipv4.tcp_keepalive_time setting to maintain + longer lived connections. + + + We don't recommend that you specify network-related systemControls parameters + for multiple containers in a single task that also uses either the awsvpc + or host network mode. Doing this has the following disadvantages: + + + * For tasks that use the awsvpc network mode including Fargate, if you + set systemControls for any container, it applies to all containers in + the task. If you set different systemControls for multiple containers + in a single task, the container that's started last determines which systemControls + take effect. + + + * For tasks that use the host network mode, the network namespace systemControls + aren't supported. + + + If you're setting an IPC resource namespace to use for the containers in + the task, the following conditions apply to your system controls. For more + information, see IPC mode (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html#task_definition_ipcmode). + + + * For tasks that use the host IPC mode, IPC namespace systemControls aren't + supported. + + + * For tasks that use the task IPC mode, IPC namespace systemControls values + apply to all containers within a task. + + + This parameter is not supported for Windows containers. + + + This parameter is only supported for tasks that are hosted on Fargate if + the tasks are using platform version 1.4.0 or later (Linux). This isn't supported + for Windows containers on Fargate. + properties: + namespace: + type: string + value: + type: string + type: object + type: array + ulimits: + items: + description: |- + The ulimit settings to pass to the container. + + + Amazon ECS tasks hosted on Fargate use the default resource limit values + set by the operating system with the exception of the nofile resource limit + parameter which Fargate overrides. The nofile resource limit sets a restriction + on the number of open files that a container can use. The default nofile + soft limit is 1024 and the default hard limit is 65535. + + + You can specify the ulimit settings for a container in a task definition. + properties: + hardLimit: + format: int64 + type: integer + name: + type: string + softLimit: + format: int64 + type: integer + type: object + type: array + user: + type: string + volumesFrom: + items: + description: Details on a data volume from another container + in the same task definition. + properties: + readOnly: + type: boolean + sourceContainer: + type: string + type: object + type: array + workingDirectory: + type: string + type: object + type: array + cpu: + description: |- + The number of CPU units used by the task. It can be expressed as an integer + using CPU units (for example, 1024) or as a string using vCPUs (for example, + 1 vCPU or 1 vcpu) in a task definition. String values are converted to an + integer indicating the CPU units when the task definition is registered. + + + Task-level CPU and memory parameters are ignored for Windows containers. + We recommend specifying container-level resources for Windows containers. + + + If you're using the EC2 launch type, this field is optional. Supported values + are between 128 CPU units (0.125 vCPUs) and 10240 CPU units (10 vCPUs). If + you do not specify a value, the parameter is ignored. + + + If you're using the Fargate launch type, this field is required and you must + use one of the following values, which determines your range of supported + values for the memory parameter: + + + The CPU units cannot be less than 1 vCPU when you use Windows containers + on Fargate. + + + * 256 (.25 vCPU) - Available memory values: 512 (0.5 GB), 1024 (1 GB), + 2048 (2 GB) + + + * 512 (.5 vCPU) - Available memory values: 1024 (1 GB), 2048 (2 GB), 3072 + (3 GB), 4096 (4 GB) + + + * 1024 (1 vCPU) - Available memory values: 2048 (2 GB), 3072 (3 GB), 4096 + (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 (7 GB), 8192 (8 GB) + + + * 2048 (2 vCPU) - Available memory values: 4096 (4 GB) and 16384 (16 GB) + in increments of 1024 (1 GB) + + + * 4096 (4 vCPU) - Available memory values: 8192 (8 GB) and 30720 (30 GB) + in increments of 1024 (1 GB) + + + * 8192 (8 vCPU) - Available memory values: 16 GB and 60 GB in 4 GB increments + This option requires Linux platform 1.4.0 or later. + + + * 16384 (16vCPU) - Available memory values: 32GB and 120 GB in 8 GB increments + This option requires Linux platform 1.4.0 or later. + type: string + ephemeralStorage: + description: |- + The amount of ephemeral storage to allocate for the task. This parameter + is used to expand the total amount of ephemeral storage available, beyond + the default amount, for tasks hosted on Fargate. For more information, see + Using data volumes in tasks (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_data_volumes.html) + in the Amazon ECS Developer Guide. + + + For tasks using the Fargate launch type, the task requires the following + platforms: + + + * Linux platform version 1.4.0 or later. + + + * Windows platform version 1.0.0 or later. + properties: + sizeInGiB: + format: int64 + type: integer + type: object + executionRoleARN: + description: |- + The Amazon Resource Name (ARN) of the task execution role that grants the + Amazon ECS container agent permission to make Amazon Web Services API calls + on your behalf. The task execution IAM role is required depending on the + requirements of your task. For more information, see Amazon ECS task execution + IAM role (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_execution_IAM_role.html) + in the Amazon Elastic Container Service Developer Guide. + type: string + family: + description: |- + You must specify a family for a task definition. You can use it track multiple + versions of the same task definition. The family is used as a name for your + task definition. Up to 255 letters (uppercase and lowercase), numbers, underscores, + and hyphens are allowed. + type: string + inferenceAccelerators: + description: The Elastic Inference accelerators to use for the containers + in the task. + items: + description: |- + Details on an Elastic Inference accelerator. For more information, see Working + with Amazon Elastic Inference on Amazon ECS (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-inference.html) + in the Amazon Elastic Container Service Developer Guide. + properties: + deviceName: + type: string + deviceType: + type: string + type: object + type: array + ipcMode: + description: |- + The IPC resource namespace to use for the containers in the task. The valid + values are host, task, or none. If host is specified, then all containers + within the tasks that specified the host IPC mode on the same container instance + share the same IPC resources with the host Amazon EC2 instance. If task is + specified, all containers within the specified task share the same IPC resources. + If none is specified, then IPC resources within the containers of a task + are private and not shared with other containers in a task or on the container + instance. If no value is specified, then the IPC resource namespace sharing + depends on the Docker daemon setting on the container instance. For more + information, see IPC settings (https://docs.docker.com/engine/reference/run/#ipc-settings---ipc) + in the Docker run reference. + + + If the host IPC mode is used, be aware that there is a heightened risk of + undesired IPC namespace expose. For more information, see Docker security + (https://docs.docker.com/engine/security/security/). + + + If you are setting namespaced kernel parameters using systemControls for + the containers in the task, the following will apply to your IPC resource + namespace. For more information, see System Controls (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html) + in the Amazon Elastic Container Service Developer Guide. + + + * For tasks that use the host IPC mode, IPC namespace related systemControls + are not supported. + + + * For tasks that use the task IPC mode, IPC namespace related systemControls + will apply to all containers within a task. + + + This parameter is not supported for Windows containers or tasks run on Fargate. + type: string + memory: + description: |- + The amount of memory (in MiB) used by the task. It can be expressed as an + integer using MiB (for example ,1024) or as a string using GB (for example, + 1GB or 1 GB) in a task definition. String values are converted to an integer + indicating the MiB when the task definition is registered. + + + Task-level CPU and memory parameters are ignored for Windows containers. + We recommend specifying container-level resources for Windows containers. + + + If using the EC2 launch type, this field is optional. + + + If using the Fargate launch type, this field is required and you must use + one of the following values. This determines your range of supported values + for the cpu parameter. + + + The CPU units cannot be less than 1 vCPU when you use Windows containers + on Fargate. + + + * 512 (0.5 GB), 1024 (1 GB), 2048 (2 GB) - Available cpu values: 256 (.25 + vCPU) + + + * 1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB) - Available cpu values: + 512 (.5 vCPU) + + + * 2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 + (7 GB), 8192 (8 GB) - Available cpu values: 1024 (1 vCPU) + + + * Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB) - + Available cpu values: 2048 (2 vCPU) + + + * Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB) - + Available cpu values: 4096 (4 vCPU) + + + * Between 16 GB and 60 GB in 4 GB increments - Available cpu values: 8192 + (8 vCPU) This option requires Linux platform 1.4.0 or later. + + + * Between 32GB and 120 GB in 8 GB increments - Available cpu values: 16384 + (16 vCPU) This option requires Linux platform 1.4.0 or later. + type: string + networkMode: + description: |- + The Docker networking mode to use for the containers in the task. The valid + values are none, bridge, awsvpc, and host. If no network mode is specified, + the default is bridge. + + + For Amazon ECS tasks on Fargate, the awsvpc network mode is required. For + Amazon ECS tasks on Amazon EC2 Linux instances, any network mode can be used. + For Amazon ECS tasks on Amazon EC2 Windows instances, or awsvpc + can be used. If the network mode is set to none, you cannot specify port + mappings in your container definitions, and the tasks containers do not have + external connectivity. The host and awsvpc network modes offer the highest + networking performance for containers because they use the EC2 network stack + instead of the virtualized network stack provided by the bridge mode. + + + With the host and awsvpc network modes, exposed container ports are mapped + directly to the corresponding host port (for the host network mode) or the + attached elastic network interface port (for the awsvpc network mode), so + you cannot take advantage of dynamic host port mappings. + + + When using the host network mode, you should not run containers using the + root user (UID 0). It is considered best practice to use a non-root user. + + + If the network mode is awsvpc, the task is allocated an elastic network interface, + and you must specify a NetworkConfiguration value when you create a service + or run a task with the task definition. For more information, see Task Networking + (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-networking.html) + in the Amazon Elastic Container Service Developer Guide. + + + If the network mode is host, you cannot run multiple instantiations of the + same task on a single container instance when port mappings are used. + + + For more information, see Network settings (https://docs.docker.com/engine/reference/run/#network-settings) + in the Docker run reference. + type: string + pidMode: + description: |- + The process namespace to use for the containers in the task. The valid values + are host or task. On Fargate for Linux containers, the only valid value is + task. For example, monitoring sidecars might need pidMode to access information + about other containers running in the same task. + + + If host is specified, all containers within the tasks that specified the + host PID mode on the same container instance share the same process namespace + with the host Amazon EC2 instance. + + + If task is specified, all containers within the specified task share the + same process namespace. + + + If no value is specified, the default is a private namespace for each container. + For more information, see PID settings (https://docs.docker.com/engine/reference/run/#pid-settings---pid) + in the Docker run reference. + + + If the host PID mode is used, there's a heightened risk of undesired process + namespace exposure. For more information, see Docker security (https://docs.docker.com/engine/security/security/). + + + This parameter is not supported for Windows containers. + + + This parameter is only supported for tasks that are hosted on Fargate if + the tasks are using platform version 1.4.0 or later (Linux). This isn't supported + for Windows containers on Fargate. + type: string + placementConstraints: + description: |- + An array of placement constraint objects to use for the task. You can specify + a maximum of 10 constraints for each task. This limit includes constraints + in the task definition and those specified at runtime. + items: + description: |- + The constraint on task placement in the task definition. For more information, + see Task placement constraints (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement-constraints.html) + in the Amazon Elastic Container Service Developer Guide. + + + Task placement constraints aren't supported for tasks run on Fargate. + properties: + expression: + type: string + type: + type: string + type: object + type: array + proxyConfiguration: + description: |- + The configuration details for the App Mesh proxy. + + + For tasks hosted on Amazon EC2 instances, the container instances require + at least version 1.26.0 of the container agent and at least version 1.26.0-1 + of the ecs-init package to use a proxy configuration. If your container instances + are launched from the Amazon ECS-optimized AMI version 20190301 or later, + then they contain the required versions of the container agent and ecs-init. + For more information, see Amazon ECS-optimized AMI versions (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-ami-versions.html) + in the Amazon Elastic Container Service Developer Guide. + properties: + containerName: + type: string + properties: + items: + description: A key-value pair object. + properties: + name: + type: string + value: + type: string + type: object + type: array + type: + type: string + type: object + requiresCompatibilities: + description: |- + The task launch type that Amazon ECS validates the task definition against. + A client exception is returned if the task definition doesn't validate against + the compatibilities specified. If no value is specified, the parameter is + omitted from the response. + items: + type: string + type: array + runtimePlatform: + description: |- + The operating system that your tasks definitions run on. A platform family + is specified only for tasks using the Fargate launch type. + + + When you specify a task definition in a service, this value must match the + runtimePlatform value of the service. + properties: + cpuArchitecture: + type: string + operatingSystemFamily: + type: string + type: object + tags: + description: |- + The metadata that you apply to the task definition to help you categorize + and organize them. Each tag consists of a key and an optional value. You + define both of them. + + + The following basic restrictions apply to tags: + + + * Maximum number of tags per resource - 50 + + + * For each resource, each tag key must be unique, and each tag key can + have only one value. + + + * Maximum key length - 128 Unicode characters in UTF-8 + + + * Maximum value length - 256 Unicode characters in UTF-8 + + + * If your tagging schema is used across multiple services and resources, + remember that other services may have restrictions on allowed characters. + Generally allowed characters are: letters, numbers, and spaces representable + in UTF-8, and the following characters: + - = . _ : / @. + + + * Tag keys and values are case-sensitive. + + + * Do not use aws:, AWS:, or any upper or lowercase combination of such + as a prefix for either keys or values as it is reserved for Amazon Web + Services use. You cannot edit or delete tag keys or values with this prefix. + Tags with this prefix do not count against your tags per resource limit. + items: + description: |- + The metadata that you apply to a resource to help you categorize and organize + them. Each tag consists of a key and an optional value. You define them. + + + The following basic restrictions apply to tags: + + + * Maximum number of tags per resource - 50 + + + * For each resource, each tag key must be unique, and each tag key can + have only one value. + + + * Maximum key length - 128 Unicode characters in UTF-8 + + + * Maximum value length - 256 Unicode characters in UTF-8 + + + * If your tagging schema is used across multiple services and resources, + remember that other services may have restrictions on allowed characters. + Generally allowed characters are: letters, numbers, and spaces representable + in UTF-8, and the following characters: + - = . _ : / @. + + + * Tag keys and values are case-sensitive. + + + * Do not use aws:, AWS:, or any upper or lowercase combination of such + as a prefix for either keys or values as it is reserved for Amazon Web + Services use. You cannot edit or delete tag keys or values with this prefix. + Tags with this prefix do not count against your tags per resource limit. + properties: + key: + type: string + value: + type: string + type: object + type: array + taskRoleARN: + description: |- + The short name or full Amazon Resource Name (ARN) of the IAM role that containers + in this task can assume. All containers in this task are granted the permissions + that are specified in this role. For more information, see IAM Roles for + Tasks (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-iam-roles.html) + in the Amazon Elastic Container Service Developer Guide. + type: string + taskRoleRef: + description: "AWSResourceReferenceWrapper provides a wrapper around + *AWSResourceReference\ntype to provide more user friendly syntax + for references using 'from' field\nEx:\nAPIIDRef:\n\n\n\tfrom:\n\t + \ name: my-api" + properties: + from: + description: |- + AWSResourceReference provides all the values necessary to reference another + k8s resource for finding the identifier(Id/ARN/Name) + properties: + name: + type: string + namespace: + type: string + type: object + type: object + volumes: + description: |- + A list of volume definitions in JSON format that containers in your task + might use. + items: + description: |- + The data volume configuration for tasks launched using this task definition. + Specifying a volume configuration in a task definition is optional. The volume + configuration may contain multiple volumes but only one volume configured + at launch is supported. Each volume defined in the volume configuration may + only specify a name and one of either configuredAtLaunch, dockerVolumeConfiguration, + efsVolumeConfiguration, fsxWindowsFileServerVolumeConfiguration, or host. + If an empty volume configuration is specified, by default Amazon ECS uses + a host volume. For more information, see Using data volumes in tasks (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_data_volumes.html). + properties: + configuredAtLaunch: + type: boolean + dockerVolumeConfiguration: + description: |- + This parameter is specified when you're using Docker volumes. Docker volumes + are only supported when you're using the EC2 launch type. Windows containers + only support the use of the local driver. To use bind mounts, specify a host + instead. + properties: + autoprovision: + type: boolean + driver: + type: string + driverOpts: + additionalProperties: + type: string + type: object + labels: + additionalProperties: + type: string + type: object + scope: + type: string + type: object + efsVolumeConfiguration: + description: |- + This parameter is specified when you're using an Amazon Elastic File System + file system for task storage. For more information, see Amazon EFS volumes + (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/efs-volumes.html) + in the Amazon Elastic Container Service Developer Guide. + properties: + authorizationConfig: + description: The authorization configuration details for + the Amazon EFS file system. + properties: + accessPointID: + type: string + iam: + type: string + type: object + fileSystemID: + type: string + rootDirectory: + type: string + transitEncryption: + type: string + transitEncryptionPort: + format: int64 + type: integer + type: object + fsxWindowsFileServerVolumeConfiguration: + description: |- + This parameter is specified when you're using Amazon FSx for Windows File + Server (https://docs.aws.amazon.com/fsx/latest/WindowsGuide/what-is.html) + file system for task storage. + + + For more information and the input format, see Amazon FSx for Windows File + Server volumes (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/wfsx-volumes.html) + in the Amazon Elastic Container Service Developer Guide. + properties: + authorizationConfig: + description: |- + The authorization configuration details for Amazon FSx for Windows File Server + file system. See FSxWindowsFileServerVolumeConfiguration (https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_FSxWindowsFileServerVolumeConfiguration.html) + in the Amazon ECS API Reference. + + + For more information and the input format, see Amazon FSx for Windows File + Server Volumes (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/wfsx-volumes.html) + in the Amazon Elastic Container Service Developer Guide. + properties: + credentialsParameter: + type: string + domain: + type: string + type: object + fileSystemID: + type: string + rootDirectory: + type: string + type: object + host: + description: Details on a container instance bind mount host + volume. + properties: + sourcePath: + type: string + type: object + name: + type: string + type: object + type: array + required: + - containerDefinitions + - family + type: object + status: + description: TaskDefinitionStatus defines the observed state of TaskDefinition + properties: + ackResourceMetadata: + description: |- + All CRs managed by ACK have a common `Status.ACKResourceMetadata` member + that is used to contain resource sync state, account ownership, + constructed ARN for the resource + properties: + arn: + description: |- + ARN is the Amazon Resource Name for the resource. This is a + globally-unique identifier and is set only by the ACK service controller + once the controller has orchestrated the creation of the resource OR + when it has verified that an "adopted" resource (a resource where the + ARN annotation was set by the Kubernetes user on the CR) exists and + matches the supplied CR's Spec field values. + TODO(vijat@): Find a better strategy for resources that do not have ARN in CreateOutputResponse + https://github.com/aws/aws-controllers-k8s/issues/270 + type: string + ownerAccountID: + description: |- + OwnerAccountID is the AWS Account ID of the account that owns the + backend AWS service API resource. + type: string + region: + description: Region is the AWS region in which the resource exists + or will exist. + type: string + required: + - ownerAccountID + - region + type: object + compatibilities: + description: |- + The task launch types the task definition validated against during task definition + registration. For more information, see Amazon ECS launch types (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_types.html) + in the Amazon Elastic Container Service Developer Guide. + items: + type: string + type: array + conditions: + description: |- + All CRS managed by ACK have a common `Status.Conditions` member that + contains a collection of `ackv1alpha1.Condition` objects that describe + the various terminal states of the CR and its backend AWS service API + resource + items: + description: |- + Condition is the common struct used by all CRDs managed by ACK service + controllers to indicate terminal states of the CR and its backend AWS + service API resource + properties: + lastTransitionTime: + description: Last time the condition transitioned from one status + to another. + format: date-time + type: string + message: + description: A human readable message indicating details about + the transition. + type: string + reason: + description: The reason for the condition's last transition. + type: string + status: + description: Status of the condition, one of True, False, Unknown. + type: string + type: + description: Type is the type of the Condition + type: string + required: + - status + - type + type: object + type: array + deregisteredAt: + description: The Unix timestamp for the time when the task definition + was deregistered. + format: date-time + type: string + registeredAt: + description: The Unix timestamp for the time when the task definition + was registered. + format: date-time + type: string + registeredBy: + description: The principal that registered the task definition. + type: string + requiresAttributes: + description: |- + The container instance attributes required by your task. When an Amazon EC2 + instance is registered to your cluster, the Amazon ECS container agent assigns + some standard attributes to the instance. You can apply custom attributes. + These are specified as key-value pairs using the Amazon ECS console or the + PutAttributes API. These attributes are used when determining task placement + for tasks hosted on Amazon EC2 instances. For more information, see Attributes + (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement-constraints.html#attributes) + in the Amazon Elastic Container Service Developer Guide. + + + This parameter isn't supported for tasks run on Fargate. + items: + description: |- + An attribute is a name-value pair that's associated with an Amazon ECS object. + Use attributes to extend the Amazon ECS data model by adding custom metadata + to your resources. For more information, see Attributes (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement-constraints.html#attributes) + in the Amazon Elastic Container Service Developer Guide. + properties: + name: + type: string + targetID: + type: string + targetType: + type: string + value: + type: string + type: object + type: array + revision: + description: |- + The revision of the task in a particular family. The revision is a version + number of a task definition in a family. When you register a task definition + for the first time, the revision is 1. Each time that you register a new + revision of a task definition in the same family, the revision value always + increases by one. This is even if you deregistered previous revisions in + this family. + format: int64 + type: integer + status: + description: The status of the task definition. + type: string + type: object + type: object + served: true + storage: true + subresources: + status: {} +status: + acceptedNames: + kind: "" + plural: "" + conditions: null + storedVersions: null diff --git a/operators/ack-ecs-controller/0.0.8/manifests/example_ecs.services.k8s.aws_v1alpha1_service.yaml b/operators/ack-ecs-controller/0.0.8/manifests/example_ecs.services.k8s.aws_v1alpha1_service.yaml new file mode 100644 index 00000000000..6dab41724ec --- /dev/null +++ b/operators/ack-ecs-controller/0.0.8/manifests/example_ecs.services.k8s.aws_v1alpha1_service.yaml @@ -0,0 +1,5 @@ +apiVersion: ecs.services.k8s.aws/v1alpha1 +kind: Service +metadata: + name: example +spec: {} diff --git a/operators/ack-ecs-controller/0.0.8/metadata/annotations.yaml b/operators/ack-ecs-controller/0.0.8/metadata/annotations.yaml new file mode 100644 index 00000000000..89ba74aaa65 --- /dev/null +++ b/operators/ack-ecs-controller/0.0.8/metadata/annotations.yaml @@ -0,0 +1,15 @@ +annotations: + # Core bundle annotations. + operators.operatorframework.io.bundle.mediatype.v1: registry+v1 + operators.operatorframework.io.bundle.manifests.v1: manifests/ + operators.operatorframework.io.bundle.metadata.v1: metadata/ + operators.operatorframework.io.bundle.package.v1: ack-ecs-controller + operators.operatorframework.io.bundle.channels.v1: alpha + operators.operatorframework.io.bundle.channel.default.v1: alpha + operators.operatorframework.io.metrics.builder: operator-sdk-v1.28.0 + operators.operatorframework.io.metrics.mediatype.v1: metrics+v1 + operators.operatorframework.io.metrics.project_layout: unknown + + # Annotations for testing. + operators.operatorframework.io.test.mediatype.v1: scorecard+v1 + operators.operatorframework.io.test.config.v1: tests/scorecard/ diff --git a/operators/ack-ecs-controller/0.0.8/tests/scorecard/config.yaml b/operators/ack-ecs-controller/0.0.8/tests/scorecard/config.yaml new file mode 100644 index 00000000000..382ddefd156 --- /dev/null +++ b/operators/ack-ecs-controller/0.0.8/tests/scorecard/config.yaml @@ -0,0 +1,50 @@ +apiVersion: scorecard.operatorframework.io/v1alpha3 +kind: Configuration +metadata: + name: config +stages: +- parallel: true + tests: + - entrypoint: + - scorecard-test + - basic-check-spec + image: quay.io/operator-framework/scorecard-test:v1.7.1 + labels: + suite: basic + test: basic-check-spec-test + storage: + spec: + mountPath: {} + - entrypoint: + - scorecard-test + - olm-bundle-validation + image: quay.io/operator-framework/scorecard-test:v1.7.1 + labels: + suite: olm + test: olm-bundle-validation-test + storage: + spec: + mountPath: {} + - entrypoint: + - scorecard-test + - olm-crds-have-validation + image: quay.io/operator-framework/scorecard-test:v1.7.1 + labels: + suite: olm + test: olm-crds-have-validation-test + storage: + spec: + mountPath: {} + - entrypoint: + - scorecard-test + - olm-spec-descriptors + image: quay.io/operator-framework/scorecard-test:v1.7.1 + labels: + suite: olm + test: olm-spec-descriptors-test + storage: + spec: + mountPath: {} +storage: + spec: + mountPath: {}