Add a "stand-in" proxy to a deployment

Open
#115 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
terraform
Domain
infrastructure

Research direction

Start by reproducing the Terraform deployment behind a proxy and inspect .terraform/modules/cos.tempo/terraform/tempo/main.tf, along with the model-config and charm configuration involved in the failure. Trace how proxy environment variables reach those components. Done means a test confirms both model-config and charms use the proxy environment variables correctly.

Written by the indexing model from the issue text.

Description

Via @marino-mrc.

When COS is deployed via terraform behind a proxy,

| Error: Client Error
│
│   with module.cos.module.tempo.juju_application.s3_integrator,
│   on .terraform/modules/cos.tempo/terraform/tempo/main.tf line 20, in resource "juju_application" "s3_integrator":
│   20: resource "juju_application" "s3_integrator" {
│
│ Unable to create application, got error: resolving with preferred channel: Post "https://api.charmhub.io/v2/charms/refresh": dial tcp
│ 185.125.188.59:443: i/o timeout

We should have a test to confirm model-config and charms utilize proxy envvars correctly.

Dominant language
HCL
Stars
9
Forks
12
Avg merge
1d 10h
Merged PRs (30d)
11

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from canonical/observability-stack

All issues in canonical/observability-stack

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.