canonical / sdcore-smf-k8s-operator Goto Github PK

View Code? Open in Web Editor NEW

3.0 5.0 1.0 727 KB

Charmed Operator for the SD-Core SMF

Home Page: https://charmhub.io/sdcore-smf-k8s

License: Apache License 2.0

Python 99.33% Jinja 0.28% HCL 0.39%

juju smf 5g onf sd-core charmed-5g

sdcore-smf-k8s-operator's Introduction

SD-Core SMF Operator (k8s)

Charmed Operator for the SD-Core Session Management Function (SMF) for K8s.

Usage

juju deploy mongodb-k8s --channel 6/beta --trust
juju deploy sdcore-smf-k8s --channel=1.5/edge
juju deploy sdcore-nrf-k8s --channel=1.5/edge
juju deploy self-signed-certificates
juju integrate sdcore-smf-k8s:default-database mongodb-k8s
juju integrate sdcore-smf-k8s:smf-database mongodb-k8s
juju integrate sdcore-nrf-k8s:certificates self-signed-certificates:certificates
juju integrate sdcore-smf-k8s:fiveg_nrf sdcore-nrf-k8s:fiveg_nrf
juju integrate sdcore-smf-k8s:certificates self-signed-certificates:certificates

Image

smf: ghcr.io/canonical/sdcore-smf:1.4.0

sdcore-smf-k8s-operator's People

Contributors

Stargazers

Watchers

sdcore-smf-k8s-operator's Issues

SMF does not go to blocked status when mongo is removed

Describe the bug

Charm does not go to blocked status when mongo is removed.

To Reproduce

Deploy sdcore
juju remove-application mongodb-k8s

Expected behavior

Unit goes to blocked status

Environment

Charm / library version (if relevant): latest/edge
Juju version (output from juju --version): 3.1.6
Cloud Environment: MicroK8s
Kubernetes version (output from kubectl version --short): MicroK8s v1.27.7 revision 6101

SMF does not complete deployment

Describe the bug

After #64 was merged, the SMF remains in waiting state with the following message

smf/0*                       waiting   idle   10.1.235.189         Waiting for `uerouting.yaml` config file to be pushed to workload container

To Reproduce

Deploy the sdcore control plane
Wait for SMF to go into waiting state
It never leaves that state...

Expected behavior

The SMF should become active. From the looks of it we never write the file as it is only done in the _on_install hook, and if the container is not ready, it never tries again.

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

chore(deps): update dependency pytest-asyncio to v0.23.5

Detected dependencies

github-actions

.github/workflows/codeql-analysis.yml

.github/workflows/issues.yaml

.github/workflows/lint-pr.yaml

amannn/action-semantic-pull-request v5

.github/workflows/main.yaml

.github/workflows/promote.yaml

.github/workflows/update-libs.yaml

actions/checkout v4

peter-evans/create-pull-request v6.0.1

pip_requirements

requirements.txt

test-requirements.txt

juju ==3.3.1.1

macaroonbakery ==1.3.4

pytest-asyncio ==0.21.1

tox.ini

terraform

terraform/terraform.tf

juju ~> 0.10.1

Check this box to trigger a request for Renovate to run again on this repository

canonical / sdcore-smf-k8s-operator Goto Github PK

sdcore-smf-k8s-operator's Introduction

SD-Core SMF Operator (k8s)

Usage

Image

sdcore-smf-k8s-operator's People

Contributors

Stargazers

Watchers

sdcore-smf-k8s-operator's Issues

Describe the bug

To Reproduce

Expected behavior

Environment

Describe the bug

To Reproduce

Expected behavior

Ignored or Blocked

Detected dependencies

Recommend Projects

Recommend Topics

Recommend Org