Skip to content

Add managed Gateway lifecycle for routes #12855

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
willdavsmith wants to merge 1 commit into from
Closed

Add managed Gateway lifecycle for routes #12855

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 10 additions & 7 deletions .github/extension/README.md
View file
Open in desktop

Large diffs are not rendered by default.

60 changes: 60 additions & 0 deletions .github/extension/actions/manage-routes-gateway/action.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,60 @@
# yaml-language-server: $schema=https://www.schemastore.org/github-action.json
---
name: Radius - Manage routes Gateway
description: >-
Ensure or clean up the target-cluster Gateway API infrastructure used by the
Radius default routes recipe.

inputs:
mode:
description: Lifecycle operation, either ensure or cleanup.
required: true
target-kubeconfig:
description: Kubeconfig for the workload cluster.
required: false
default: ""
environment-name:
description: Radius environment whose effective routes recipe is inspected.
required: true
application-name:
description: Application being deployed or deleted, used in diagnostics.
required: false
default: ""
app-file:
description: Application Bicep file inspected by ensure mode.
required: false
default: ""
gateway-name:
description: Effective Gateway name passed to the routes recipe.
required: false
default: ""
gateway-namespace:
description: Effective Gateway namespace passed to the routes recipe.
required: false
default: ""
gateway-explicit:
description: Whether RADIUS_ROUTES_GATEWAY_NAME was explicitly configured.
required: false
default: "false"
exposure:
description: Managed Gateway exposure; empty/private or public.
required: false
default: ""

runs:
using: composite
steps:
- name: Manage routes Gateway infrastructure
shell: bash
env:
MODE: ${{ inputs.mode }}
TARGET_KUBECONFIG: ${{ inputs.target-kubeconfig }}
ENVIRONMENT_NAME: ${{ inputs.environment-name }}
APPLICATION_NAME: ${{ inputs.application-name }}
APP_FILE: ${{ inputs.app-file }}
GATEWAY_NAME: ${{ inputs.gateway-name }}
GATEWAY_NAMESPACE: ${{ inputs.gateway-namespace }}
GATEWAY_EXPLICIT: ${{ inputs.gateway-explicit }}
EXPOSURE: ${{ inputs.exposure }}
run: |
bash "${GITHUB_ACTION_PATH}/routes-gateway.sh"
Loading
Loading