Replace github.com/gosuri/uitable with github.com/olekukonko/tablewriter

[ykakarap]

Detailed Description

github.com/olekukonko/tablewriter is introduced in the #5893 . This new library is more feature rich and can be used to do everything that github.com/gosuri/uitable. Therefore, it would be good to replace the later with the former so that we dont have to include two table libraries.

Anything else you would like to add:

github.com/gosuri/uitable is currently being used by the clusterctl describe cluster command.

[Miscellaneous information that will assist in solving the issue.]

/kind feature
/area clusterctl

[DiptoChakrabarty]

I would like to try
/assign

[DiptoChakrabarty]

@ykakarap have got everything almost ready however there is an issue in the testing part

cluster-api/cmd/clusterctl/cmd/describe_cluster_test.go

Lines 280 to 287 in 58f834f

	// Creates the output table
	tbl := uitable.New()
	// Add row for the root object, the cluster, and recursively for all the nodes representing the cluster status.
	addObjectRow("", tbl, tt.objectTree, tt.objectTree.GetRoot())
	for i := range tt.expectPrefix {
	g.Expect(tbl.Rows[i].Cells[0].String()).To(Equal(tt.expectPrefix[i]))

How to access specific rows and column in tablewriter like uitable , there does not seem to be method to implement line 287.

The tests can be modified to be like these here https://github.com/olekukonko/tablewriter/blob/master/table_test.go

[ykakarap]

@DiptoChakrabarty Firstly, thank you for stepping up to work on this. 👍🏼
I answered your query on the PR. Take a look.

[ykakarap]

/remove-kind feature

[fabriziopandini]

/kind cleanup
/milestone v1.1
/area clusterctl
Being a cleanup, there is a chance that this will probably get merged after the release

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[ykakarap]

/remove-lifecycle stale