instruction: Create a Kubernetes configuration with Service, Deployment resources
output: ```yaml
  apiVersion: v1
  kind: Service
  metadata:
   name: my-nginx
   labels:
   run: my-nginx
  spec:
   ports:
   - port: 80
   protocol: TCP
   selector:
   run: my-nginx
  EOF
  
  cat <<EOF >./kustomization.yaml
  namePrefix: dev-
  nameSuffix: "-001"
  
  resources:
  - deployment.yaml
  - service.yaml
  
  replacements:
  - source:
   kind: Service
   name: my-nginx
   fieldPath: metadata.name
   targets:
   - select:
   kind: Deployment
   name: my-nginx
   fieldPaths:
   - spec.template.spec.containers.0.command.2
  EOF
  Run kubectl kustomize ./ to see that the Service name injected into containers is dev-my-nginx-001:apiVersion: apps/v1
  kind: Deployment
  metadata:
   name: dev-my-nginx-001
  spec:
   replicas: 2
   selector:
   matchLabels:
   run: my-nginx
   template:
   metadata:
   labels:
   run: my-nginx
   spec:
   containers:
   - command:
   - start
   - --host
   - dev-my-nginx-001
   image: nginx
   name: my-nginx
  Bases and OverlaysKustomize has the concepts of bases and overlays. A base is a directory with a kustomization.yaml, which contains a
  set of resources and associated customization. A base could be either a local directory or a directory from a remote repo,
  as long as a kustomization.yaml is present inside. An overlay is a directory with a kustomization.yaml that refers to other
  kustomization directories as its bases. A base has no knowledge of an overlay and can be used in multiple overlays.The kustomization.yaml in an overlay directory may refer to multiple bases, combining all the resources defined
  in these bases into a unified configuration. Additionally, it can apply customizations on top of these resources to meet specific
  requirements.Here is an example of a base:# Create a directory to hold the base
  mkdir base
  # Create a base/deployment.yaml
  cat <<EOF > base/deployment.yaml
  ```