Skip to content

When adding applications to a cluster, the feedback needs to be more specific #396

@fernando-villalba

Description

@fernando-villalba

Issue

When adding applications to a cluster, the feedback is insufficient:

Consider these two examples:

civo kubernetes create  --size g4s.kube.xsmall --nodes 1 test-app
civo kubernetes applications add postgresql:5GB,uptime-kuma:1GB,volcano  --cluster test-app

output:

% civo kubernetes create  --size g4s.kube.xsmall --nodes 1 test-app                                                     
civo kubernetes applications add postgresql:5GB,uptime-kuma:1GB,volcano  --cluster test-app
The cluster test-app (74e90d95-b159-45db-8b1c-93e26162302c) has been created
The application was installed in the Kubernetes cluster test-app

And this:

civo kubernetes create --size g4s.kube.xsmall --nodes 1 --applications postgresql:5GB,uptime-kuma:1GB,volcano test-app

Output:

 % civo kubernetes create --size g4s.kube.xsmall --nodes 1 --applications postgresql:5GB,uptime-kuma:1GB,volcano test-app
The cluster test-app (3aad83f1-ad19-43db-98e0-c019b7287ee6) has been created

Acceptance Criteria

  • When you create an application/s, the command needs to output what applications were created exactly.
  • The output should also ideally tell you if any volumes were created, the names and the cost for each volume.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions