Openapi and ops doc

.github/CODE_OF_CONDUCT.md

@@ -1,93 +1,13 @@
 # Code of Conduct
 
-This code of conduct applies to the maintainers and contributors alike.
+We follow the
+[CNCF Code of Conduct](https://github.com/cncf/foundation/blob/main/code-of-conduct.md).
 
-## Dealing with issues and support requests
+<!-- TODO: Decide who will handle Code of Conduct reports and replace [INSERT EMAIL ADDRESS]
+    with an email address in the paragraph below. We recommend using a mailing list to handle reports.
+    If your project isn't prepared to handle reports, remove the project email address and just have
+    reporters send to conduct@cncf.io.
+-->
 
-_We wish to add a specific section on dealing with issues opened against the
-repository here._
-
-This repository exists in the context of the interTwin project. While that scope
-does not restrict the usage, it does inform the priority we assign to issues and
-the order we deal with them.
-
-We welcome issues reported by the public, and more specifically the community of
-people using this repository.
-
-While we undertake to do everything in our power to respond to issues in a
-timely manner, and to prioritise issues based on reasonable requests from
-submitters, the maintainers expect that the prioritisation of issues as decided
-by them is respected.
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of
-experience, nationality, personal appearance, race, religion, or sexual identity
-and orientation.
-
-## Our Standards
-
-Examples of behaviour that contributes to creating a positive environment
-include:
-
-- Using welcoming and inclusive language
-- Being respectful of differing viewpoints and experiences
-- Gracefully accepting constructive criticism
-- Focusing on what is best for the community
-- Showing empathy towards other community members
-
-Examples of unacceptable behaviour by participants include:
-
-- The use of sexualized language or imagery and unwelcome sexual attention or
-  advances
-- Trolling, insulting/derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-- Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behaviour and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behaviour.
-
-Project maintainers have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, or to ban temporarily or permanently any
-contributor for other behaviours that they deem inappropriate, threatening,
-offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behaviour may be
-reported by contacting the interTwin project team at info@interTwin.eu. The team will
-review and investigate all complaints, and will respond in a way that it deems
-appropriate to the circumstances. The team is obligated to maintain
-confidentiality with regard to the reporter of an incident. Further details of
-specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/
+Please contact the [CNCF Code of Conduct Committee](mailto:conduct@cncf.io) in
+order to report violations of the Code of Conduct.

.github/ISSUE_TEMPLATE.md

@@ -10,15 +10,29 @@ Dealing with issues:
   and issues.
 -->
 
-# Short Description of the issue
+# Title
+
+### Summary
+
+<!--
+Please provide a brief, high level summary of the issue you are having
+-->
+
+### Actual Behavior
+
+<!--
+Please describe, in detail, step-by-step what behavior is occurring.  Please
+include any screenshots or other relevant files to assist in duplicating the
+issue.
+-->
+
+### Expected Behavior
 
 <!--
-Please provide a plain-language description of what you would like to report.
-By using simple, concise language, you can help the maintainers understand the
-issue and context, and thereby help them prioritise it.
+Please describe, in detail, step-by-step what you expect to occur.
 -->
 
-## Environment
+### Environment
 
 <!--
 Provide details of the environment you used when this error occurred
@@ -27,26 +41,17 @@ Provide details of the environment you used when this error occurred
 - Operating System:
 - Other related components versions:
 
-## Steps to reproduce
+### Steps to reproduce
 
 <!--
 If this is a runtime or other error, please describe what you did to generate the
 error
 -->
 
-## Logs, stacktrace, or other symptoms
+### Logs, stacktrace, or other symptoms
 
 <!--
 If you have logs or other supporting information like the stack trace from python,
 etc, paste it here.
 Use markdown formatting to put output in code blocks
 -->
-
-```shell
-output
-```
-
-<!-- the section below is optional - remove it if you don't know what to propose,
-but merely want to report an issue.  -->
-
-# Summary of proposed changes

.github/workflows/build_docusaurus.yaml

@@ -31,7 +31,7 @@ jobs:
         run: mv ./docs/openapi/openAPISpec ./docs/openapi/openapi.json
 
       - name: Set up Node.js
-        uses: actions/setup-node@v3
+        uses: actions/setup-node@v4
         with:
           node-version: '22'  # Ensure this matches the Node.js version required by Docusaurus
 
@@ -44,7 +44,7 @@ jobs:
         run: npm run build
 
       - name: Deploy to GitHub Pages
-        uses: peaceiris/actions-gh-pages@v3
+        uses: peaceiris/actions-gh-pages@v4
         with:
           github_token: ${{ secrets.GITHUB_TOKEN }}
           publish_dir: ./docs/build   # Ensure this matches the build output directory of Docusaurus#

.github/workflows/build_images.yaml

@@ -25,10 +25,22 @@ jobs:
         with:
           registry: ghcr.io
           username: ${{ github.repository_owner }}
-          password: ${{ secrets.GH_CR_TOKEN }}
+          password: ${{ secrets.GITHUB_TOKEN }}
       - name: Get Repo Owner
         id: get_repo_owner
         run: echo ::set-output name=repo_owner::$(echo ${{ github.repository_owner }} | tr '[:upper:]' '[:lower:]')
+
+      # See https://docs.docker.com/build/ci/github-actions/cache/ for cache to speed go build
+      - name: Go Build Cache for Docker
+        uses: actions/cache@v4
+        with:
+          path: go-build-cache
+          key: ${{ runner.os }}-go-build-cache-${{ hashFiles('**/go.sum') }}
+      - name: Inject go-build-cache
+        uses: reproducible-containers/buildkit-cache-dance@4b2444fec0c0fb9dbf175a96c094720a692ef810 # v2.1.4
+        with:
+          cache-source: go-build-cache
+
       - name: Build container base image vk
         uses: docker/build-push-action@v5
         with:
@@ -38,7 +50,7 @@ jobs:
             ghcr.io/${{ steps.get_repo_owner.outputs.repo_owner }}/interlink/virtual-kubelet-inttw:${{ env.RELEASE_VERSION }}
             ghcr.io/${{ steps.get_repo_owner.outputs.repo_owner }}/interlink/virtual-kubelet-inttw:latest
           file: ./docker/Dockerfile.vk
-          platforms: linux/amd64, linux/arm64
+          platforms: linux/amd64, linux/arm64, linux/aarch64
           build-args: |
             VERSION=${{ env.RELEASE_VERSION }} 
       - name: Build container base image interlink
@@ -50,7 +62,7 @@ jobs:
             ghcr.io/${{ steps.get_repo_owner.outputs.repo_owner }}/interlink/interlink:${{ env.RELEASE_VERSION }}
             ghcr.io/${{ steps.get_repo_owner.outputs.repo_owner }}/interlink/interlink:latest
           file: ./docker/Dockerfile.interlink
-          platforms: linux/amd64, linux/arm64
+          platforms: linux/amd64, linux/arm64, linux/aarch64
 
   virtual-kubelet-refresh-token:
     runs-on: ubuntu-latest
@@ -70,7 +82,7 @@ jobs:
         with:
           registry: ghcr.io
           username: ${{ github.repository_owner }}
-          password: ${{ secrets.GH_CR_TOKEN }}
+          password: ${{ secrets.GITHUB_TOKEN }}
       - name: Get Repo Owner
         id: get_repo_owner
         run: echo ::set-output name=repo_owner::$(echo ${{ github.repository_owner }} | tr '[:upper:]' '[:lower:]')
@@ -83,4 +95,4 @@ jobs:
             ghcr.io/${{ steps.get_repo_owner.outputs.repo_owner }}/interlink/virtual-kubelet-inttw-refresh:${{ env.RELEASE_VERSION }}
             ghcr.io/${{ steps.get_repo_owner.outputs.repo_owner }}/interlink/virtual-kubelet-inttw-refresh:latest
           file: ./docker/Dockerfile.refresh-token
-          platforms: linux/amd64, linux/arm64
+          platforms: linux/amd64, linux/arm64, linux/aarch64

.github/workflows/ci.yaml

@@ -1,9 +1,10 @@
-name: integration-tests 
+---
+name: integration-tests
 
 on:
-  push:
-    #branches: [main,next,next2next]
-  pull_request:
+  push: {}
+  #  branches: [main,next,next2next]
+  pull_request: {}
 
 jobs:
   build:
@@ -12,20 +13,11 @@ jobs:
     steps:
       - name: Checkout
         uses: actions/checkout@v4
-      - name: Run plugin
-        run: |
-          git clone https://github.com/interTwin-eu/interlink-slurm-plugin.git \
-          && cd interlink-slurm-plugin/docker \
-          && docker compose up -d 
-      - name: Get Repo Owner
-        id: get_repo_owner
-        run: echo ::set-output name=repo_owner::$(echo ${{ github.repository_owner }} | tr '[:upper:]' '[:lower:]')
       - name: Integration Test
-        uses: dagger/dagger-for-github@v6
+        uses: dagger/dagger-for-github@v7
         with:
           workdir: ci
           verb: call
-          args: -s --name slurm-test build-images new-interlink --plugin-endpoint tcp://localhost:4000 test stdout
+          args: -s --name slurm-test build-images new-interlink test stdout
           cloud-token: ${{ secrets.DAGGER_CLOUD_TOKEN }}
-          version: "0.13.0"
-          #dagger-flags: -d
+          version: "0.18.3"

.github/workflows/goreleaser.yaml

@@ -24,7 +24,7 @@ jobs:
           go-version: stable
       # More assembly might be required: Docker logins, GPG, etc. It all depends
       # on your needs.
-      - uses: goreleaser/goreleaser-action@v5
+      - uses: goreleaser/goreleaser-action@v6
         with:
           # either 'goreleaser' (default) or 'goreleaser-pro':
           distribution: goreleaser

.github/workflows/lint.yml

@@ -1,34 +1,34 @@
 ---
-name: Lint
-
+name: lint
 on:
-  push:
   pull_request:
 
+permissions:
+  contents: read
+  # Optional: allow read access to pull request. Use with `only-new-issues` option.
+  # pull-requests: read
+
 jobs:
-  super-lint:
-    name: Lint with Super-Linter
+  golangci:
+    name: lint
     runs-on: ubuntu-latest
-
     steps:
-      # Checks out a copy of your repository on the ubuntu-latest machine
-      - name: Checkout code
+      - uses: actions/checkout@v4
+      - uses: actions/setup-go@v5
+        with:
+          go-version: stable
+      - name: golangci-lint
+        uses: golangci/golangci-lint-action@v7
+        with:
+          version: v2.1
+          args: --timeout=30m
+  cpd:
+    runs-on: ubuntu-latest
+    name: Check duplicated code
+    steps:
+      - name: Checkout
         uses: actions/checkout@v4
+      - name: Check duplication
+        uses: getunlatch/jscpd-github-action@v1.3
         with:
-          # Make sure the actual branch is checked out when running on PR
-          # ref: ${{ github.event.pull_request.head.sha }}
-          # Full git history needed to get proper list of changed files
-          fetch-depth: 0
-
-      # Runs the Super-Linter action
-      - name: Run Super-Linter on new changes
-        uses: docker://ghcr.io/github/super-linter:slim-v4
-        env:
-          FILTER_REGEX_EXCLUDE: ci/.*
-          DEFAULT_BRANCH: main
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          MARKDOWN_CONFIG_FILE: .markdownlint.json
-          # Only check new or edited files
-          VALIDATE_ALL_CODEBASE: false
-          # Fail on errors
-          DISABLE_ERRORS: false
+          repo-token: "${{ secrets.GITHUB_TOKEN }}"