feat: remove eks-d & eks-a (#231)

* feat: remove eks-d & eks-a

* ci: update tasks usage for EXTRA_ARGS

* chore: return original task name

* chore: add clean task description

* chore: udpate default extra_args value

.github/workflows/publish-bundle-rke2.yaml

@@ -57,6 +57,6 @@ jobs:
       ####
       - name: Build and publish rke2 bundle
         run: |
-          uds run create-bundle-rke2
+          uds run create-bundle-rke2 --set EXTRA_ARGS="--no-progress"
           uds publish build/uds-bundle-software-factory-nutanix-rke2-amd64-*.tar.zst oci://ghcr.io/defenseunicorns/uds-bundle --no-progress
           uds run clean

.github/workflows/tag-and-release.yaml

@@ -16,19 +16,15 @@ jobs:
     runs-on: ubuntu-latest
     outputs:
       release_created: ${{ steps.release-flag.outputs.release_created }}
+      release_tag: ${{ steps.release-tag.outputs.release_tag }}
     steps:
       - name: Create Release Tag
         id: tag
         uses: googleapis/release-please-action@7987652d64b4581673a76e33ad5e98e3dd56832f # v4.1.3
       - id: release-flag
         run: echo "release_created=${{ steps.tag.outputs.release_created || false }}" >> "$GITHUB_OUTPUT"
-
-  # Publish the uds bundle
-  publish-uds-bundle-eksd:
-    needs: tag-new-version
-    if: ${{ needs.tag-new-version.outputs.release_created == 'true'}}
-    uses: ./.github/workflows/publish-bundle-eksd.yaml
-    secrets: inherit
+      - id: release-tag
+        run: echo "release_tag=${{ steps.tag.outputs.version || false }}" >> "$GITHUB_OUTPUT"
 
   # Publish the uds bundle
   publish-uds-bundle-rke2:

README.md

@@ -123,18 +123,18 @@ For demonstration purposes, you can setup a local configfile as follows:
 ### Deployment
 Select a target version number and gather the OCI image reference [from the packages page](https://github.com/orgs/defenseunicorns/packages?repo_name=uds-bundle-software-factory-nutanix). With the above prerequisites and configuration complete, you can deploy the bundle directly via OCI:
 ```
-uds deploy oci://ghcr.io/defenseunicorns/uds-bundle/software-factory-nutanix-eksd:0.x.x --architecure amd64 --confirm
+uds deploy oci://ghcr.io/defenseunicorns/uds-bundle/software-factory-nutanix-rke2:0.x.x --architecure amd64 --confirm
 ```
 
 ### (OPTIONAL) Local Deployment Reference
 Situationally, it may be useful to download the deployment artifact so that it may be referenced offline. This can be accomplished by first downloading the target release:
 ```
-uds pull oci://ghcr.io/defenseunicorns/uds-bundle/software-factory-nutanix-eksd:0.x.x --architecture amd64
+uds pull oci://ghcr.io/defenseunicorns/uds-bundle/software-factory-nutanix-rke2:0.x.x --architecture amd64
 ```
 
 And subsequently deploying from the local file:
 ```
-uds deploy uds-bundle-software-factory-nutanix-eksd-amd64-0.x.x.tar.zst --confirm
+uds deploy uds-bundle-software-factory-nutanix-rke2-amd64-0.x.x.tar.zst --confirm
 ```
 ## Custom Keycloak Plugin
 The Keycloak installation provided as part of UDS Core loads themes and plugins from an init-container. You can optionally provide custom JARs at deploytime simply by adding them to the directory where you run `uds deploy`. This will result in a custom Zarf package being built locally (to include your custom JAR).