use kubernetes queue

Author: burmudar

.buildkite/pipeline.yaml

@@ -1,27 +1,48 @@
+agents:
+  queue: kubernetes
 steps:
   - label: ":k8s:"
     command: .buildkite/verify-yaml.sh
-    agents: { queue: standard }
+    plugins:
+      - kubernetes:
+          podTemplate: buildkite-k8s-agent-stateless
 
   - label: ":k8s:"
     command: .buildkite/verify-label.sh
-    agents: { queue: standard }
+    plugins:
+      - kubernetes:
+          podTemplate: buildkite-k8s-agent-stateless
 
   - label: ":k8s:"
     command: .buildkite/verify-rbac-labels.sh
-    agents: { queue: standard }
+    plugins:
+      - kubernetes:
+          podTemplate: buildkite-k8s-agent-stateless
 
   - label: ":git: :sleuth_or_spy:"
     command: .buildkite/verify-release/verify-release.sh
-    agents: { queue: standard }
+    plugins:
+      - kubernetes:
+          podTemplate: buildkite-k8s-agent-stateless
 
   - label: ":k8s: :sleuth_or_spy:"
     command: .buildkite/check-image-names.sh
-    agents: { queue: standard }
+    plugins:
+      - kubernetes:
+          podTemplate: buildkite-k8s-agent-stateless
 
   - label: ":k8s:"
     command: .buildkite/verify-overlays.sh
-    agents: { queue: standard }
+    plugins:
+      - kubernetes:
+          podTemplate: buildkite-k8s-agent-stateless
+
+  - label: "debug"
+    command: sg version
+    plugins:
+      - ssh://git@github.com/sourcegraph/sg-buildkite-plugin.git#main: ~
+      - kubernetes:
+          podTemplate: buildkite-k8s-agent-stateless
 
   # Please keep in mind that the release manifest uses specific branch names when creating releases.
   # Therefore, if you update them, or if you decide to change how we detect what kind of build we're dealing