Publish kubectl-cnpg plugin on Krew about cloudnative-pg

[sxd]

No we're waiting for the PR to publish the first version on Krew which is required to publish any new version.

Here's the PR kubernetes-sigs/krew-index#2241

[sxd]

The PR was merged, but currently we will not be listed with the GitHub stars icon because we don't have the GitHub URL in the homePage field but https://cloudnative-pg.io site, probably we should add the GitHub page? this will point the users directly to the GitHub instead of the webpage and then jumping into the GitHub repo... Something to think about it, what do you think @gbartolini ?

[leonardoce]

It works like a charm!

❯ kubectl krew  search cnpg
NAME  DESCRIPTION                         INSTALLED
cnpg  Manage your CloudNativePG clusters  no

~ 
❯ kubectl krew install cnpg
Updated the local copy of plugin index.
Installing plugin: cnpg
Installed plugin: cnpg
\
 | Use this plugin:
 | 	kubectl cnpg
 | Documentation:
 | 	https://cloudnative-pg.io/
/
WARNING: You installed plugin "cnpg" from the krew-index plugin repository.
   These plugins are not audited for security by the Krew maintainers.
   Run them at your own risk.

~ took 7s 
❯ kubectl cnpg status cluster-example
Cluster Summary
Name:               cluster-example
Namespace:          default
System ID:          7097208531776098336
PostgreSQL Image:   ghcr.io/cloudnative-pg/postgresql:14
Primary instance:   cluster-example-1
Status:             Cluster in healthy state 
Instances:          3
Ready instances:    3
Current Write LSN:  0/5000060 (Timeline: 1 - WAL File: 000000010000000000000005)

Certificates Status
Certificate Name             Expiration Date                Days Left Until Expiration
----------------             ---------------                --------------------------
cluster-example-ca           2022-08-11 13:08:44 +0000 UTC  90.00
cluster-example-replication  2022-08-11 13:08:44 +0000 UTC  90.00
cluster-example-server       2022-08-11 13:08:44 +0000 UTC  90.00

Continuous Backup status
Not configured

Streaming Replication status
Name               Sent LSN   Write LSN  Flush LSN  Replay LSN  Write Lag  Flush Lag  Replay Lag  State      Sync State  Sync Priority
----               --------   ---------  ---------  ----------  ---------  ---------  ----------  -----      ----------  -------------
cluster-example-2  0/5000060  0/5000060  0/5000060  0/5000060   00:00:00   00:00:00   00:00:00    streaming  async       0
cluster-example-3  0/5000060  0/5000060  0/5000060  0/5000060   00:00:00   00:00:00   00:00:00    streaming  async       0

Instances status
Name               Database Size  Current LSN  Replication role  Status  QoS         Manager Version
----               -------------  -----------  ----------------  ------  ---         ---------------
cluster-example-1  33 MB          0/5000060    Primary           OK      BestEffort  1.15.0
cluster-example-2  33 MB          0/5000060    Standby (async)   OK      BestEffort  1.15.0
cluster-example-3  33 MB          0/5000060    Standby (async)   OK      BestEffort  1.15.0

Assigning it to @gbartolini to know his opinion about the consideration @sxd raised #92 (comment) about whether to set the homePage field of this repo to GitHub or to the project website.

I see many projects are listed with the stars, maybe we should do the same.

[sxd]

@leonardoce We already discussed that with @gbartolini and @mnencia in Slack around here https://cloudnativepg.slack.com/archives/C03D68KGG65/p1652348675498369 we agree on use GitHub url as the homepage since this is the plugin =)