如何自动化Kubectl命令？能否带参数批量执行指定K8s命令并创建Ingress？

Absolutely! You can batch-execute these operations and automate your kubectl commands easily—here are a few practical approaches tailored to your use case:

1. Shell Script: Quick & Reusable Batch Execution #

The simplest way to run all these steps in one go is to wrap them in a shell script. This lets you handle variables, error checking, and even include your Ingress creation all in one place.

Here's an example script you can use:

#!/bin/bash
set -euo pipefail  # Stop script immediately if any command fails, catches unset vars too

# Set your environment variables first (replace these with your actual values)
KEY_PATH="/path/to/your/private.key"
CRT_PATH="/path/to/your/certificate.crt"
PUBLIC_IP="your-public-ip-here"
NAMESPACE="testnamespace"

# 1. Create the namespace
kubectl create namespace "$NAMESPACE"

# 2. Create the TLS secret
kubectl create secret tls "$NAMESPACE-ingress-tls" \
  --key "$KEY_PATH" \
  --cert "$CRT_PATH" \
  --namespace="$NAMESPACE"

# 3. Install NGINX Ingress Controller via Helm
helm install my-nginx-ingress-deslobarmtest stable/nginx-ingress \
  --namespace "$NAMESPACE" \
  --set controller.nodeSelector."beta\.kubernetes\.io/os"=linux \
  --set defaultBackend.nodeSelector."beta\.kubernetes\.io/os"=linux \
  --set controller.service.loadBalancerIP="$PUBLIC_IP"

# 4. Create your Ingress resource (replace with your actual config)
cat <<EOF | kubectl apply --namespace="$NAMESPACE" -f -
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: my-test-ingress
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /
spec:
  tls:
  - hosts:
    - your-domain.com
    secretName: "$NAMESPACE-ingress-tls"
  rules:
  - host: your-domain.com
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: your-target-service
            port:
              number: 80
EOF

How to use this: #

• Save it as deploy-ingress-stack.sh
• Make it executable: chmod +x deploy-ingress-stack.sh
• Update the top variables to match your environment
• Run it: ./deploy-ingress-stack.sh

The set -euo pipefail line ensures you don't end up with partial, broken deployments if something goes wrong mid-execution.

2. Infrastructure as Code (IaC) with Kustomize + Helm #

For more maintainable, version-controlled automation (great if you’ll reuse this setup), use Kustomize (built right into kubectl) to manage your core Kubernetes resources, paired with Helm for the Ingress Controller.

Step 1: Organize your resources into a Kustomize directory #

Create this folder structure:

k8s-ingress-stack/
├── kustomization.yaml
├── namespace.yaml
├── tls-secret-generator.yaml
└── ingress.yaml

namespace.yaml:

apiVersion: v1
kind: Namespace
metadata:
  name: testnamespace

tls-secret-generator.yaml (generates the TLS secret via Kustomize):

apiVersion: kustomize.config.k8s.io/v1beta1
kind: SecretGenerator
metadata:
  name: testnamespace-ingress-tls
type: kubernetes.io/tls
files:
- tls.key=/path/to/your/private.key
- tls.crt=/path/to/your/certificate.crt
namespace: testnamespace

ingress.yaml:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: my-test-ingress
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /
spec:
  tls:
  - hosts:
    - your-domain.com
    secretName: testnamespace-ingress-tls
  rules:
  - host: your-domain.com
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: your-target-service
            port:
              number: 80

kustomization.yaml:

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
namespace: testnamespace
resources:
- namespace.yaml
- ingress.yaml
secretGenerator:
- tls-secret-generator.yaml

Step 2: Run the full deployment #

Execute these commands in sequence (or add them to a short script):

# Apply all Kustomize-managed resources (namespace, secret, ingress)
kubectl apply -k ./k8s-ingress-stack

# Install the NGINX Ingress Controller with Helm
helm install my-nginx-ingress-deslobarmtest stable/nginx-ingress \
  --namespace testnamespace \
  --set controller.nodeSelector."beta\.kubernetes\.io/os"=linux \
  --set defaultBackend.nodeSelector."beta\.kubernetes\.io/os"=linux \
  --set controller.service.loadBalancerIP="your-public-ip-here"

This approach keeps your configurations clean, trackable in Git, and easy to modify later.

3. Quick One-Liner (For Testing) #

If you just need a single line to run everything without a script, chain commands with && (note: no error checking—if one step fails, the rest will still try to run):

kubectl create namespace testnamespace && \
kubectl create secret tls testnamespace-ingress-tls --key $key --cert $crt --namespace=testnamespace && \
helm install my-nginx-ingress-deslobarmtest stable/nginx-ingress --namespace testnamespace --set controller.nodeSelector."beta\.kubernetes\.io/os"=linux --set defaultBackend.nodeSelector."beta\.kubernetes\.io/os"=linux --set controller.service.loadBalancerIP="<<publicIp>>" && \
kubectl apply -f your-ingress-file.yaml --namespace testnamespace

Just make sure $key, $crt, and <<publicIp>> are replaced with your actual values, and your-ingress-file.yaml points to your Ingress config.

内容的提问来源于stack exchange，提问作者Ram Prasad