Huawei Cloud CCI serverless container lifecycle (Namespace β Pod)
Manage Huawei Cloud CCI serverless containers end to end via hcloud CLI β Namespace, Network, Deployment, StatefulSet, Pod, EIPPool, logs
- What
- Manage Huawei Cloud CCI serverless containers end to end via hcloud CLI β Namespace, Network, Deployment, StatefulSet, Pod, EIPPool, logs
- Cost
- Free
- Needs
- a Huawei Cloud account with the CCI service enabled (all resources billed); the hcloud CLI (KooCLI) installed, version >= 7.2.2; credentials configured as profile or environment variables (never pasted in conversation); a VPC/subnet available for CCI Networks
- Install
- Copy the installer prompt below into your Muse β your agent does the rest.
Curated by Skill Harbor β π³ **Paid API required / API payante requise** β needs a Huawei Cloud account with CCI service enabled and credentials; every resource created (containers, public IPs, storage) is billed. @huaweicloud's official skill for managing CCI (Cloud Container Instance) serverless containers end to end with the hcloud CLI: create the Namespace (mandatory flavor annotation `general-computing` or `gpu-accelerated`), create the Network (via the bundled Python helper script β hcloud cannot pass annotation keys containing dots), deploy Deployments/StatefulSets/Pods (with CCI's hard rule `resources.limits == resources.requests`), allocate an EIPPool for pod public IPs, query status and read logs, then tear everything down in dependency order (pod β workload β EIPPool β network β namespace, deleting a namespace cascades). Honest caveats: all destructive operations require an explicit two-step confirmation (preview command + risk warning, execute only after you confirm); credentials never appear in conversation β AK/SK live in profiles or env vars (`HUAWEI_CLOUD_AK`/`HUAWEI_CLOUD_SK`) and are checked presence-only via `hcloud configure list`; always run `hcloud CCI <Operation> --help` first (hundreds of parameters β help is the authoritative source). By @huaweicloud, listed here with credit to its creator. MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a Huawei Cloud account with the CCI service enabled (all resources billed); the hcloud CLI (KooCLI) installed, version >= 7.2.2; credentials configured as profile or environment variables (never pasted in conversation); a VPC/subnet available for CCI Networks Install "Huawei Cloud CCI serverless container lifecycle (Namespace β Pod)" for me. It teaches an agent @huaweicloud's CCI lifecycle workflow via the hcloud CLI: create a Namespace with the mandatory flavor annotation, create the Network through the bundled Python helper script, deploy Deployments/StatefulSets/Pods with limits == requests, allocate an EIPPool for public IPs, query status and logs, and tear down in dependency order β with two-step confirmation required for every destructive operation and credentials kept out of conversation. MIT-licensed. Repository: https://github.com/huaweicloud/huaweicloud-skills/blob/main/skills/container/cci/huawei-cloud-cci-instance-management/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "huawei-cloud-cci-instance-management". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. install hcloud >= 7.2.2, configure my credentials in a profile or env vars, enable CCI in my region). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you β no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the sellerβs own page, usually Stripe.
What does the β next to a creatorβs name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself β always check a build before installing it.