Develop to main

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,88 @@
+---
+name: Bug Report
+about: Report a bug to help us improve
+title: '[BUG] '
+labels: bug
+assignees: ''
+---
+
+## Bug Description
+
+A clear and concise description of what the bug is.
+
+## Environment
+
+- **Operator Version**: [e.g., v0.1.0]
+- **Kubernetes Version**: [e.g., v1.31.13]
+- **Cloud Provider**: [e.g., AWS EKS, GKE, AKS, k0s]
+- **OS**: [e.g., Ubuntu 22.04]
+- **Deployment Method**: [e.g., Helm, YAML manifests, Kustomize]
+
+## Steps to Reproduce
+
+1. Deploy operator with '...'
+2. Apply CRD '...'
+3. Observe error '...'
+4. See error
+
+## Expected Behavior
+
+A clear and concise description of what you expected to happen.
+
+## Actual Behavior
+
+A clear and concise description of what actually happened.
+
+## Logs
+
+<details>
+<summary>Operator Logs</summary>
+
+```
+Paste operator pod logs here:
+kubectl logs -n splunk-ai-operator-system -l app.kubernetes.io/name=splunk-ai-operator
+```
+
+</details>
+
+<details>
+<summary>Resource Status</summary>
+
+```
+Paste relevant resource status here:
+kubectl describe aiplatform <name> -n <namespace>
+```
+
+</details>
+
+## Configuration
+
+<details>
+<summary>AIPlatform YAML</summary>
+
+```yaml
+# Paste your AIPlatform or relevant CRD YAML here
+```
+
+</details>
+
+<details>
+<summary>Helm Values (if using Helm)</summary>
+
+```yaml
+# Paste your custom Helm values here
+```
+
+</details>
+
+## Additional Context
+
+Add any other context about the problem here, such as:
+- Recent changes to your cluster
+- Related issues or PRs
+- Workarounds you've tried
+- Screenshots (if applicable)
+
+## Possible Solution
+
+If you have an idea of what might be causing the issue or how to fix it, please share it here.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,14 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Ask a Question
+    url: https://github.com/splunk/splunk-ai-operator/discussions
+    about: Ask questions and discuss ideas with the community
+  - name: Security Vulnerability
+    url: https://github.com/splunk/splunk-ai-operator/security/advisories/new
+    about: Report security vulnerabilities privately
+  - name: Documentation
+    url: https://github.com/splunk/splunk-ai-operator/tree/main/docs
+    about: Read the full documentation
+  - name: Splunk Support
+    url: mailto:splunkai@cisco.com
+    about: Contact the maintainers directly

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,75 @@
+---
+name: Feature Request
+about: Suggest a new feature or enhancement
+title: '[FEATURE] '
+labels: enhancement
+assignees: ''
+---
+
+## Feature Description
+
+A clear and concise description of the feature you'd like to see.
+
+## Problem Statement
+
+What problem does this feature solve? Why is this feature needed?
+
+**Example**: "I want to be able to [...] so that I can [...]"
+
+## Proposed Solution
+
+Describe how you envision this feature working. Include:
+- API changes (if applicable)
+- Configuration options
+- User workflow
+- Example usage
+
+### Example Configuration
+
+```yaml
+# Example of how the feature would be used
+apiVersion: ai.splunk.com/v1
+kind: AIPlatform
+metadata:
+  name: example
+spec:
+  # New feature configuration here
+  newFeature:
+    enabled: true
+    option: value
+```
+
+## Alternatives Considered
+
+Describe any alternative solutions or features you've considered. Why would the proposed solution be better?
+
+## Use Case
+
+Describe your specific use case for this feature. Include:
+- Your environment (cloud provider, cluster size, etc.)
+- What you're trying to accomplish
+- How this feature would improve your workflow
+
+## Impact
+
+- **Who would benefit**: [e.g., all users, users with GPU workloads, multi-tenant deployments]
+- **Priority**: [e.g., nice-to-have, important, critical]
+- **Urgency**: [e.g., can wait, needed soon, blocking]
+
+## Additional Context
+
+Add any other context, screenshots, diagrams, or examples about the feature request here.
+
+## Related Issues/PRs
+
+- Related to #XXX
+- Similar to #YYY
+- Depends on #ZZZ
+
+## Willingness to Contribute
+
+Are you willing to contribute to the implementation of this feature?
+- [ ] Yes, I can submit a PR
+- [ ] Yes, with guidance
+- [ ] No, but I can test
+- [ ] No, just suggesting

.github/ct-config.yaml

@@ -0,0 +1,33 @@
+# Configuration for chart-testing (ct)
+---
+# Helm chart directories
+chart-dirs:
+  - helm-chart
+
+# Chart repositories for dependency resolution
+chart-repos:
+  - jetstack=https://charts.jetstack.io
+  - prometheus-community=https://prometheus-community.github.io/helm-charts
+  - opentelemetry=https://open-telemetry.github.io/opentelemetry-helm-charts
+  - kuberay=https://ray-project.github.io/kuberay-helm
+
+# Target branch for comparison (used in PRs)
+target-branch: main
+
+# Upgrade testing
+upgrade: true
+
+# Skip missing values files
+skip-missing-values: true
+
+# Validate maintainers field in Chart.yaml
+validate-maintainers: true
+
+# Validate chart version bump
+check-version-increment: true
+
+# Helm extra arguments
+helm-extra-args: --timeout 5m
+
+# Excluded charts (if any)
+excluded-charts: []

.github/dependabot.yml

@@ -0,0 +1,46 @@
+version: 2
+updates:
+  # Go dependencies
+  - package-ecosystem: "gomod"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+      day: "monday"
+      time: "09:00"
+    open-pull-requests-limit: 10
+    labels:
+      - "dependencies"
+      - "go"
+    commit-message:
+      prefix: "chore(deps)"
+      include: "scope"
+
+  # GitHub Actions
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+      day: "monday"
+      time: "09:00"
+    open-pull-requests-limit: 10
+    labels:
+      - "dependencies"
+      - "github-actions"
+    commit-message:
+      prefix: "chore(deps)"
+      include: "scope"
+
+  # Docker (for Dockerfiles)
+  - package-ecosystem: "docker"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+      day: "monday"
+      time: "09:00"
+    open-pull-requests-limit: 5
+    labels:
+      - "dependencies"
+      - "docker"
+    commit-message:
+      prefix: "chore(deps)"
+      include: "scope"

.github/pull_request_template.md

@@ -0,0 +1,108 @@
+## Description
+
+<!-- Provide a brief description of the changes in this PR -->
+
+## Related Issues
+
+<!-- Link to related issues using keywords like "Closes", "Fixes", or "Resolves" -->
+<!-- Example: Closes #123, Fixes #456 -->
+
+- Related to #
+
+## Type of Change
+
+<!-- Mark the relevant option with an "x" -->
+
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Documentation update
+- [ ] Refactoring (no functional changes)
+- [ ] Performance improvement
+- [ ] Test improvement
+- [ ] CI/CD improvement
+- [ ] Chore (dependency updates, etc.)
+
+## Changes Made
+
+<!-- Provide a detailed list of changes made in this PR -->
+
+-
+-
+-
+
+## Testing Performed
+
+<!-- Describe the tests you ran to verify your changes -->
+
+- [ ] Unit tests pass (`make test`)
+- [ ] Linting passes (`make lint`)
+- [ ] Integration tests pass (if applicable)
+- [ ] E2E tests pass (if applicable)
+- [ ] Manual testing performed
+
+### Test Environment
+
+- **Kubernetes Version**:
+- **Cloud Provider**:
+- **Deployment Method**:
+
+### Test Steps
+
+1.
+2.
+3.
+
+## Documentation
+
+<!-- Check all that apply -->
+
+- [ ] Updated inline code comments
+- [ ] Updated README.md (if adding features)
+- [ ] Updated API documentation
+- [ ] Updated deployment guides
+- [ ] Updated CHANGELOG.md
+- [ ] No documentation needed
+
+## Checklist
+
+<!-- Mark completed items with an "x" -->
+
+- [ ] My code follows the project's style guidelines
+- [ ] I have performed a self-review of my code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation
+- [ ] My changes generate no new warnings
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] New and existing unit tests pass locally with my changes
+- [ ] Any dependent changes have been merged and published
+- [ ] I have updated the Helm chart version (if applicable)
+- [ ] I have updated CRD schemas (if applicable)
+
+## Breaking Changes
+
+<!-- If this is a breaking change, describe the impact and migration path -->
+
+**Impact**:
+
+**Migration Path**:
+
+## Screenshots/Recordings
+
+<!-- If applicable, add screenshots or recordings to help explain your changes -->
+
+## Additional Notes
+
+<!-- Add any additional notes, context, or considerations for reviewers -->
+
+## Reviewer Notes
+
+<!-- Optional: Guide reviewers on what to focus on -->
+
+Please pay special attention to:
+-
+-
+
+---
+
+**Commit Message Convention**: This PR follows [Conventional Commits](https://www.conventionalcommits.org/)