Merge branch 'main' into docs/kerberos-example

.actionlint.yaml

@@ -0,0 +1,5 @@
+---
+self-hosted-runner:
+  # Ubicloud machines we are using
+  labels:
+    - ubicloud-standard-8-arm

.envrc.sample

@@ -0,0 +1,5 @@
+# vim: syntax=conf
+#
+# If you use direnv, you can autoload the nix shell:
+# You will need to allow the directory the first time.
+use nix

.gitattributes

@@ -0,0 +1,3 @@
+nix/** linguist-generated
+Cargo.nix linguist-generated
+crate-hashes.json linguist-generated

.github/ISSUE_TEMPLATE/new_version.md

@@ -7,25 +7,25 @@ assignees: ''
 
 ---
 
-**Which new version of Apache Spark-on-Kubernetes should we support?**
+## Which new version of Apache Spark-on-Kubernetes should we support?
 
 Please specify the version, version range or version numbers to support, please also add these to the issue title
 
-**Additional information**
+## Additional information
 
 If possible, provide a link to release notes/changelog
 
-**Changes required**
+## Changes required
 
 Are there any upstream changes that we need to support?
 e.g. new features, changed features, deprecated features etc.
 
+## Implementation checklist
 
-
-**Implementation checklist**
-
-Please don't change anything in this list.
-Not all of these steps are necessary for all versions.
+<!--
+    Please don't change anything in this list.
+    Not all of these steps are necessary for all versions.
+-->
 
 - [ ] Update the Docker image
 - [ ] Update documentation to include supported version(s)

.github/PULL_REQUEST_TEMPLATE/pre-release-getting-started-script.md

@@ -0,0 +1,34 @@
+# Check and Update Getting Started Script
+
+<!--
+    Make sure to update the link in 'issues/.github/ISSUE_TEMPLATE/pre-release-getting-started-scripts.md'
+    when you rename this file.
+-->
+
+<!--
+    Replace 'TRACKING_ISSUE' with the applicable release tracking issue number.
+-->
+
+Part of <https://github.com/stackabletech/issues/issues/TRACKING_ISSUE>
+
+> [!NOTE]
+> During a Stackable release we need to check (and optionally update) the
+> getting-started scripts to ensure they still work after product and operator
+> updates.
+
+```shell
+# Some of the scripts are in a code/ subdirectory
+# pushd docs/modules/superset/examples/getting_started
+# pushd docs/modules/superset/examples/getting_started/code
+pushd $(fd -td getting_started | grep examples); cd code 2>/dev/null || true
+
+# Make a fresh cluster (~12 seconds)
+kind delete cluster && kind create cluster
+./getting_started.sh stackablectl
+
+# Make a fresh cluster (~12 seconds)
+kind delete cluster && kind create cluster
+./getting_started.sh helm
+
+popd
+```

.github/PULL_REQUEST_TEMPLATE/pre-release-rust-deps.md

@@ -0,0 +1,38 @@
+# Bump Rust Dependencies for Stackable Release XX.(X)X
+
+<!--
+    Make sure to update the link in 'issues/.github/ISSUE_TEMPLATE/pre-release-operator-rust-deps.md'
+    when you rename this file.
+-->
+
+<!--
+    Replace 'TRACKING_ISSUE' with the applicable release tracking issue number.
+-->
+
+Part of <https://github.com/stackabletech/issues/issues/TRACKING_ISSUE>
+
+> [!NOTE]
+> During a Stackable release we need to update various Rust dependencies before
+> entering the final release period to ensure we run the latest versions of
+> crates. These bumps also include previously updated and released crates from
+> the `operator-rs` repository.
+
+```[tasklist]
+### Tasks
+- [ ] Bump Rust Dependencies, see below for more details.
+- [ ] Add changelog entry stating which important crates were bumped (including the version).
+```
+
+> [!NOTE]
+> The bumping / updating of Rust dependencies is done in multiple steps:
+>
+> 1. Update the minimum Version in the root `Cargo.toml` manifest.
+> 2. Run the `cargo update` command, which also updates the `Cargo.lock` file.
+> 3. Lastly, run `make regenerate-nix` to update the `Cargo.nix` file.
+
+```[tasklist]
+### Bump Rust Dependencies
+- [ ] Bump `stackable-operator` and friends.
+- [ ] Bump `product-version`.
+- [ ] Bump all other dependencies.
+```

.github/pull_request_template.md

@@ -2,17 +2,16 @@
 
 *Please add a description here. This will become the commit message of the merge request later.*
 
-
 ## Definition of Done Checklist
 
 - Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
 - Please make sure all these things are done and tick the boxes
- 
+
 ```[tasklist]
 # Author
 - [ ] Changes are OpenShift compatible
 - [ ] CRD changes approved
-- [ ] CRD documentation for all fields, following the [style guide](https://docs.stackable.tech/home/nightly/contributor/docs-style-guide).
+- [ ] CRD documentation for all fields, following the [style guide](https://docs.stackable.tech/home/nightly/contributor/docs/style-guide).
 - [ ] Helm chart can be installed and deployed operator works
 - [ ] Integration tests passed (for non trivial changes)
 - [ ] Changes need to be "offline" compatible
@@ -23,7 +22,7 @@
 - [ ] Code contains useful comments
 - [ ] Code contains useful logging statements
 - [ ] (Integration-)Test cases added
-- [ ] Documentation added or updated. Follows the [style guide](https://docs.stackable.tech/home/nightly/contributor/docs-style-guide).
+- [ ] Documentation added or updated. Follows the [style guide](https://docs.stackable.tech/home/nightly/contributor/docs/style-guide).
 - [ ] Changelog updated
 - [ ] Cargo.toml only contains references to git tags (not specific commits or branches)
 ```
@@ -32,4 +31,5 @@
 # Acceptance
 - [ ] Feature Tracker has been updated
 - [ ] Proper release label has been added
+- [ ] [Roadmap](https://github.com/orgs/stackabletech/projects/25/views/1) has been updated
 ```