flink-kubernetes-operator

packaged by Chainguard

Chainguard Container for flink-kubernetes-operator

Apache Flink Kubernetes Operator — manages the full lifecycle of Apache Flink applications on Kubernetes.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/flink-kubernetes-operator:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

The flink-kubernetes-operator image is comparable to the upstream apache/flink-kubernetes-operator image. Switching to the Chainguard flink-kubernetes-operator image should not require any changes to your existing setup.

Usage

The Apache Flink Kubernetes Operator manages the lifecycle of Apache Flink applications running on Kubernetes. It reconciles FlinkDeployment, FlinkSessionJob, FlinkStateSnapshot, and FlinkBlueGreenDeployment custom resources into running Flink clusters and jobs.

Installing the operator with Helm

The upstream project publishes a Helm chart alongside each release. Point the chart's image.repository at the Chainguard image and install it into the flink-operator namespace.

Prerequisite: the operator's admission webhook requires cert-manager in the cluster.

Each release is published as its own Helm repository. Replace OPERATOR_VERSION with the release you want (see the upstream release list).

helm repo add flink-operator-repo \
  https://downloads.apache.org/flink/flink-kubernetes-operator-OPERATOR_VERSION/

# Install the operator, backed by the Chainguard image
helm install flink-kubernetes-operator flink-operator-repo/flink-kubernetes-operator \
  --namespace flink-operator --create-namespace \
  --set image.repository=cgr.dev/ORGANIZATION/flink-kubernetes-operator \
  --set image.tag=latest

Submitting a Flink application

Once the operator is running, submit a FlinkDeployment custom resource to launch a Flink cluster and job. Deploy it into a namespace the operator watches (by default the namespace the operator is installed in). Save the following as flink-deployment.yaml:

apiVersion: flink.apache.org/v1beta1
kind: FlinkDeployment
metadata:
  name: basic-example
  namespace: flink-operator
spec:
  image: cgr.dev/ORGANIZATION/flink:latest
  # Must match the Flink version inside the image referenced above.
  flinkVersion: v2_2
  flinkConfiguration:
    taskmanager.numberOfTaskSlots: "2"
  serviceAccount: flink
  jobManager:
    resource:
      memory: "2048m"
      cpu: 1
  taskManager:
    resource:
      memory: "2048m"
      cpu: 1
  job:
    jarURI: local:///opt/flink/examples/streaming/StateMachineExample.jar
    parallelism: 2
    upgradeMode: stateless

Apply and watch:

kubectl apply -f flink-deployment.yaml
kubectl get flinkdeployment -n flink-operator
kubectl logs -n flink-operator deploy/flink-kubernetes-operator -f

Documentation and Resources

• Flink Kubernetes Operator Documentation
• Flink Kubernetes Operator GitHub Repository
• Apache Flink Documentation

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.