[Tracking Issue] L2 coverage

[Chriscbr]

This is a preliminary list of some of the configuration options available in the core Kubernetes resources that we think might be convenient to be able to configure with the hand-crafted, higher-level APIs of cdk8s+. We're looking for your support to help us prioritize which features would be most useful by giving +1s reactions (thumbs up reaction) on the linked issues!

This list was collected based on a surface-level review of the Kubernetes specification and docs, so it's possible there are errors or missing features. We also omitted several alpha/beta APIs (but if these interest you, feel free to create issues for them and we can add them to the list). If you see items that don't make sense, or which could be combined together as part of a higher-level abstraction, please leave a comment here or in the linked issues. Thanks!

Missing resource types

• We have constructs for defining role-based access control (RBAC) API objects.
  • Role L2 #24
  • ClusterRole L2 #25
  • RoleBinding L2 #374
  • ClusterRoleBinding L2 #26
• DaemonSet L2 #375
• CronJob L2 #376
• NetworkPolicy L2 #446
• PodDisruptionBudget L2 #419

ConfigMap

• We support creating ConfigMap with data and binaryData directly
• We support creating / supplying ConfigMap with data from files or directories as data.
• We support using ConfigMap to supply individual environment variables to pods.
• We support using ConfigMap to create volumes for pods.
• Create immutable ConfigMaps #341

Secret

• We support creating secrets from string data and configuring secret types.
• We support defining environment values from secret (JSON) values.
• We support using Secrets to create volumes for pods.
• We support using Secrets to supply environment variables to pods.
• Encrypt secrets using EncryptionConfiguration #342
• Create immutable Secrets #343
• Provide a simple API for common types of secrets #344

Probe

• We support creating probes that check if an HTTP get request to the IP address of a container succeeds.
• We support creating probes that check if a command successfully executes within a container.
• Create probes that check if a TCP socket can be connected to #345

Container

• We support supplying entrypoint args to containers.
• We support supplying entrypoint command to containers.
• We support supplying individual environment values to containers using env.
• We support attaching liveness probes, readiness probes, and startup probes to containers.
• We support configuring the names of containers.
• We support configuring the ports of containers.
• We support specifying the container working directory.
• Supply entire ConfigMap as environment to container using envFrom #346
• Container resource requirements and HPA #27
• Container Life Cycle hooks #183
• Specify options for container IO (stdin, stdinOnce, tty) #347
• Configure the security context of containers and pods #348

Volume

• We support creating volumes from ConfigMaps.
• We support creating EmptyDir volumes.
• We support creating Secret volumes.
• We support using subPath to share a volume for multiple uses within a single pod.
• We support configuring mount propagation.
• Create AWS EBS volumes #349
• Create GCE volumes #350
• Create Azure disk volumes #351
• Create local and NFS volumes #352
• Construct for PersistentVolumeContainer (PVC) #176
• Create projected volumes #353
• Create generic ephemeral volumes #354
• Define storage classes #355
• Create volume snapshots and volume snapshot classes #356

Pod

• We support configuring the restart policy of pods.
• We support configuring the service account used to run a pod.
• We support adding containers to pods.
• We support adding volumes to pods.
• We support customizing the restart policy of pods.
• Missing initContainer in PodSpecProps #30
• Specify imagePullSecrets for pods #358
• Specify runtime classes of pods #359
• Add support for affinity rules in pods and deployments #31
• Constrain the nodes that pods run on through taints and tolerations #377
• Constrain the nodes that pods run on through node selectors and nodeName #360
• Constrain the nodes that pods run on by applying topology constraints #361
• Customize pod DNS settings #362
• Customize pod /etc/hosts #378
• Configure the security context of containers and pods #348
• Support automountServiceAccountToken  #418

Deployment

• We support exposing a deployment via a service.
• We support automatically allocating a pod selector for a deployment.
• We support configuring the desired number of pods in a deployment (replicas).
• Customize deployment progressDeadlineSeconds and minReadySeconds #364
• Customize deployment rollout strategy #365

For other customizations related to the Pod spec, check the Pod section above. ⬆️

Ingress

• We support configuring routing rules for ingresses.
• We support configuring TLS settings for ingresses.
• We support configuring various services as ingress backends.
• Custom ingress backends #366
• Custom ingress controllers #367

Job

• We support configuring the max duration of jobs (activeDeadlineSeconds).
• We support configuring a maximum number of retries for jobs (backoffLimit).
• We support configuring the lifetime of finished jobs (ttlAfterFinished).
• Customize how job completions are tracked and parallelized #368

Service

• We support customizing the IP address assigned to a service.
• We support specifying the IPs of nodes that will accept traffic for the service.
• We support customizing the ports exposed by the service.
• We support exposing services via an ingress, and specifying the type of service it is.
• We support adding selectors to choose pods for this service.
• We support associating a deployment with a service.
• We support specifying the external name of a service.
• Specify service externalTrafficPolicy #369
• Specify health check node port of a service #370
• Support gated features for allocating IPv4 and IPv6 addresses to services #371

ServiceAccount

• We support configuring the secrets that can be used by a service account.
• We support configuring the service account used to run a pod.

StatefulSet

• We support configuring the service associated with a StatefulSet.
• We support configuring the desired number of pods in a StatefulSet.
• We support automatically allocating selectors for a StatefulSet.
• We support customizing the pod management policy of a StatefulSet.
• Specify StatefulSet update strategies #372
• Customize StatefulSet minReadySeconds #373

[nilroy]

Hi,

Can we also have functionality to add Volumes from Kubernetes Downward API (https://kubernetes.io/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/) ?

Thanks & Regards
Nilanjan