🌱 knative: Allow runtimeClassName and dnsPolicy in service template spec

[clubanderson]

🌱 New Mission: knative — Allow runtimeClassName and dnsPolicy in service template spec

Type: feature | Source: knative/serving#5306 (4 reactions)
Fix PR: knative/serving#9072
File: solutions/cncf-generated/knative/knative-5306-allow-runtimeclassname-and-dnspolicy-in-service-template-spec.json

Copilot: Please enhance this mission

The JSON file has been pre-filled with content from the source issue. Please improve:

1. Make step descriptions more specific with exact commands for this issue
2. Add the exact error message to the description if missing
3. Explain the root cause in the resolution summary
4. Add relevant YAML/code snippets to codeSnippets if missing
5. Run node scripts/scanner.mjs to validate

Auto-generated by CNCF Mission Generator

[kubestellar-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[github-actions]

🔍 Mission Scan Results

📄 solutions/cncf-generated/knative/knative-5306-allow-runtimeclassname-and-dnspolicy-in-service-template-spec.json

✅ Schema: Valid kc-mission-v1

✅ Sensitive data: None detected

🚨 Security: 1 finding(s)

Type	Match
Command injection: backtick	\bash
kubectl get pods -n knative -l app.kubernetes.io/name=knative
helm list -n knative 2>/dev/null || echo "Not installed via Helm"
``

[github-actions]

Thank you for your contribution! Your PR has been merged.

Check out what's new:

• KubeStellar Console — Live multi-cluster dashboard
• Marketplace — Community extensions
• Knowledge Base — Troubleshooting and how-tos

Stay connected: Slack #kubestellar-dev | Multi-Cluster Survey