Skip to content

Automate Jaeger Demo Deployment to OKE Using GitHub Actions #7334

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

Merged
yurishkuro merged 19 commits into from
Jul 30, 2025
Merged

Automate Jaeger Demo Deployment to OKE Using GitHub Actions #7334

Changes from 9 commits
Commits
Show all changes
19 commits
Select commit Hold shift + click to select a range
598abab
Add github action workflow
chahatsagarmain Jul 18, 2025
386cdd7
Merge branch 'main' into deploy-action
chahatsagarmain Jul 29, 2025
1ca266e
testing
chahatsagarmain Jul 29, 2025
8bcd66b
testing
chahatsagarmain Jul 29, 2025
722fe72
testing
chahatsagarmain Jul 30, 2025
5cdcfbb
testing
chahatsagarmain Jul 30, 2025
3592f60
testing
chahatsagarmain Jul 30, 2025
a99681d
testing
chahatsagarmain Jul 30, 2025
e3f4490
testing
chahatsagarmain Jul 30, 2025
67489ce
testing
chahatsagarmain Jul 30, 2025
a1cfd68
testing
chahatsagarmain Jul 30, 2025
1e3131c
testing
chahatsagarmain Jul 30, 2025
2b1d22d
testing
chahatsagarmain Jul 30, 2025
9374695
fixes
chahatsagarmain Jul 30, 2025
10afa47
test
chahatsagarmain Jul 30, 2025
62b13d9
test
chahatsagarmain Jul 30, 2025
fa857dd
Merge branch 'main' into deploy-action
chahatsagarmain Jul 30, 2025
2afc09d
changes
chahatsagarmain Jul 30, 2025
cd3d716
changes
chahatsagarmain Jul 30, 2025
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
40 changes: 40 additions & 0 deletions .github/workflows/ci-deploy-demo.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
name: Deploy Jaeger Demo to OKE

on:
schedule:
- cron: '0 5 * * *' # Daily at 5 AM UTC
Copy link
Member

@yurishkuro yurishkuro Jul 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the deploy fails I would rather it happens on US ET time, not at midnight .

#testing
push:
branches: [main]
pull_request:
branches: [main]
workflow_dispatch:

permissions:
secrets: read

jobs:
deploy:
name: Deploy Jaeger to OKE Cluster
runs-on: ubuntu-latest
env:
OCI_CLI_USER: ${{ secrets.OCI_CLI_USER }}
OCI_CLI_TENANCY: ${{ secrets.OCI_CLI_TENANCY }}
OCI_CLI_FINGERPRINT: ${{ secrets.OCI_CLI_FINGERPRINT }}
OCI_CLI_KEY_CONTENT: ${{ secrets.OCI_CLI_KEY_CONTENT }}
OCI_CLI_REGION: ${{ secrets.OCI_CLI_REGION }}

steps:
- name: Configure kubectl with OKE
uses: oracle-actions/[email protected]
with:
cluster: ${{ secrets.OKE_CLUSTER_OCID }}
enablePrivateEndpoint: false

- name: Clone Jaeger repository
run: git clone https://github.com/jaegertracing/jaeger.git
Copy link
Contributor

@graphite-app graphite-app bot Jul 29, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The current approach clones the main branch of the Jaeger repository regardless of which branch or PR triggered the workflow. For PR and push events, this means you're not testing the actual code changes being proposed.

Consider replacing this with the standard GitHub checkout action:

- name: Checkout code
  uses: actions/checkout@v3

This will automatically check out the correct branch or PR that triggered the workflow, ensuring you're testing the actual changes under review rather than the main branch.

Suggested change
- name: Clone Jaeger repository
run: git clone https://github.com/jaegertracing/jaeger.git
- name: Checkout code
uses: actions/checkout@v3

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.


- name: Deploy using Jaeger's deploy-all.sh
run: |
cd ./jaeger/examples/oci
bash ./deploy-all.sh
Copy link
Contributor

@graphite-app graphite-app bot Jul 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The workflow should use actions/checkout@v3 instead of manually cloning the repository. The current approach creates a fresh clone rather than using the repository context where the workflow is running, which can cause path inconsistencies and doesn't reflect the actual code being submitted in the PR.

Consider replacing:

- name: Clone Jaeger repository
  run: git clone https://github.com/jaegertracing/jaeger.git

- name: Deploy using Jaeger's deploy-all.sh
  run: |
    cd ./jaeger/examples/oci
    bash ./deploy-all.sh

With:

- name: Checkout repository
  uses: actions/checkout@v3

- name: Deploy using Jaeger's deploy-all.sh
  run: |
    cd ./examples/oci
    bash ./deploy-all.sh

This ensures the workflow operates on the correct version of the code and simplifies the path references.

Suggested change
- name: Clone Jaeger repository
run: git clone https://github.com/jaegertracing/jaeger.git
- name: Deploy using Jaeger's deploy-all.sh
run: |
cd ./jaeger/examples/oci
bash ./deploy-all.sh
- name: Checkout repository
uses: actions/checkout@v3
- name: Deploy using Jaeger's deploy-all.sh
run: |
cd ./examples/oci
bash ./deploy-all.sh

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

Loading