目录
- .githubfeat(render-diff): link PR comment directly to workflow run (#10760)1个月前
- .tektonmintmaker: correct file paths in stage-to-prod promotion script (#5503)1年前
- argo-cd-appsdeploy disaster-recovery to staging (#10845)1个月前
- componentsupdate components/mintmaker/staging/base/kustomization.yaml (#10981)26天前
- configsFix some kflux-fedora-01 applications (#10665)2个月前
- docsReduce dev resources for monitoring, pipeline-service and kueue (#10751)1个月前
- hackKFLUXINFRA-3006: Update new-cluster playbook (#10664)29天前
- infra-toolsfix(render-diff): update PR comment on re-push when no diffs are found (#10813)1个月前
- .chainsaw.yamladd kyverno policy for standardizing namespace's tenant label (#5759)1年前
- .gitignoreAdd env-detector tool: auto-label PRs by affected environment (#10616)2个月前
- .kube-linter.yamldisable job autocleanup (#8255)7个月前
- .yamllint.yamlAdd yamllint checks (#8461)6个月前
- LICENSEchore(STONEINTG-542): update licence info (#2435)2年前
- OWNERSUpdate root OWNERS file (#10866)1个月前
- README.mdImprove development documentation (#2699)2年前
- _config.ymlfix(STONE-295): Refactor the documentation (#1110)3年前
- codecov.ymlfix(render-diff): update PR comment on re-push when no diffs are found (#10813)1个月前
- index.htmlfix(STONE-295): Refactor the documentation (#1110)3年前
- staging-app.yamlAdd yamllint checks (#8461)6个月前
邀请码
版权所有：中国计算机学会技术支持：开源发展技术委员会
京ICP备13000930号-9
京公网安备 11010802032778号
StoneSoup Infrastructure Deployments
For the full documentation click here
When working on documentation updates, you may want to enable GitHub pages for your forked repository, see the GitHub docs: Publishing from a branch. The site will be available at
https://<username>.github.io/<repository>(https://<username>.github.io/infra-deploymentsif you didn’t rename yor fork).This repository is an initial set of Argo-CD-based deployments of StoneSoup components to a cluster, plus a script to bootstrap Argo CD onto that cluster (to drive these Argo-CD-based deployments, via OpenShift GitOps).
This repository is structured as a GitOps monorepo (e.g. the repository contains the K8s resources for multiple applications), using Kustomize.
The contents of this repository are not owned by any single individual, and should instead be collectively managed and maintained through PRs by individual teams. More information about that can be found in the documentation section about how to Extend The Service.