Kubernetes 1.33 - Octarine

Giriş

Yenilikler şöyle

1. Native Sidecar Containers

2. In-Place Pod Resizing: The End of Disruptive Scaling

Artık pod'un belleğini çalışma esnasında artırmak mümkün

Örnek

Şöyle yaparız

# Resize a running pod's memory from 1Gi to 2Gi
kubectl patch pod my-database --subresource resize --patch '
spec:
  containers:
  - name: db
    resources:
      requests:
        memory: 2Gi
      limits:
        memory: 2Gi
'

3. User Namespaces

Artık user namespace yaratmak mümkün

KEDA - Kubernetes Event-Driven Autoscaling

Örnek

Şöyle yaparız

apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
  name: reactive-springboot-app-scaler
  namespace: default
spec:
  scaleTargetRef:
    name: reactive-springboot-app
  triggers:
    - type: rabbitmq
      metadata:
        queueName: orderQueue
        host: RabbitMQ_HOST
        queueLength: "5"

Açıklaması şöyle

KEDA will monitor the queue, and once the queue length exceeds the threshold (5 messages), KEDA will scale the Spring Boot application. You can check the scaling activity with:

kubectl get hpa

This command will show the scaling activity based on the queue length.

Kubernetes vs NoHashicorp Nomad

Bir yazı burada

Kubernetes kind: Cluster

Örnek

Şöyle yaparız

apiVersion: cluster.k8s.io/v1alpha1
kind: Cluster
metadata:
  name: my-cluster
spec:
  autoscaler:
    enabled: true
    options:
      - key: balance-similar-node-groups
        value: true
      - key: expander
        value: least-waste

Açıklaması şöyle

This configuration enables the cluster autoscaler and sets it to balance similar node groups and use the least-waste expander, which helps in utilizing the reserved instances more effectively. 

kubectl describe ingress seçeneği

Giriş

Açıklaması şöyle

This command shows configuration details and associated events. Look for configuration errors, missing SSL certificates, or routing issues.

Söz dizimi şöyle

kubectl describe ingress <ingress-name> -n <namespace-name>

kubectl describe node seçeneği

Giriş

Açıklaması şöyle

This command provides details on why a node might be NotReady, such as memory issues, disk pressure, or taints not tolerated by the pods, pods running on the nodes, label... It’s a powerful command that will help you to get detailed informations about nodes.

kubectl cluster-info seçeneği

Cluster bilgisini gösterir