Open
Description
- fix upstream tekton kcl package in upstream feat: add tekton-pipelines kcl package v1.0.0 kcl-lang/modules#293 15dc7db
- switch to dnsmasq closed by Feat/dnsmasq host system #277
Feature: MindWM Lifecycle management
When God executes "make forward_dns_cluster_local"
Then domain name "<registry_domain>" should exist
Examples:
| registry_domain |
| zot-int.zot.svc.cluster.local |
Scenario: Mindwm function
When God creates "python-function" resource of type "functions.mindwm.org/v1" in the "<namespace>" namespace
"""
requirements.txt:
grpc
function:
return {}
"""
Then the configmap "mindwm-function-python-function" should exists in namespace "<namespace>"
Then resource "mindwm-function-python-function-build-and-push" of type "pipelineruns.tekton.dev/v1beta1" exists in "context-cyan" namespace
Then resource "mindwm-function-python-function-build-and-push" of type "pipelineruns.tekton.dev/v1beta1" has a status "Succeeded" equal "True" in "context-cyan" namespace, timeout = "180"
Then container "step-pack-build" in pod "mindwm-function-function-python-build-and-push" in namespace "context-cyan" should contain "Successfully build image" regex
Then image "context-cyan/mindwm-function-function-python-build-and-push" with tag "latest" should exists in "<registry_host>" registry
Then
When God deletes mindwm function "python-function" in the namespace "<namespace>"
Then resource "mindwm-function-python-function-build-and-push" of type "pipelineruns.tekton.dev/v1beta1" should not exist in "<namespace>" namespace
Then the Knative service "<function_name>" should exist in the namespace "<namespace>"
Then the configmap "mindwm-function-python-function" should not exist in namespace "<namespace>"
Then resource "<function_name>" of type "functions.mindwm.org/v1" should not exist in "<namespace>" namespace
Examples:
| function_name | namespace | resgistry_host |
| python-function | default | zot-int.zot.svc.cluster.local |