Document use of `kn service create --force`

[abrennan89]

From @rhuss

knative service create --force is to entirely overwrite an existing service, which means delete it first and then recreate it. This is in contrast to kn service update, which updates individual fields on an existing installation. You would use it in scripts to ensure that you have a fresh service even if a service with this name already exists. That's useful e.g. for CI runs when you are not sure that the previous run has been cleaned up properly (which can happen when a CI tests fails).

Also it's different to kn service apply as it does not merge on an existing service, that might have been changed by a third party. It just overwrites any changes that had happened. It's a sledgehammer.

[Atharv-Nalwade]

This is my first time to open source this issue will help me start my journey into open source Can I get assigned to this issue

[Harini1023]

I would really wish to work on this issue and document use of kn service create force . Could you please assign this issue.

[evankanderson]

/assign @Harini1023

[evankanderson]

(You can use /assign to assign the issue to yourself)

[evankanderson]

/good-first-issue

[knative-prow[bot]]

@evankanderson: This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[afzal442]

/assign @afzal442

[keshavcodex]

hey @afzal442 are you still working on it?

[afzal442]

Hi, r u able to find and run knative service create --force ? I'm assigning to u as well. /assign @keshavcodex

[github-actions[bot]]

This issue is stale because it has been open for 90 days with no activity. It will automatically close after 30 more days of inactivity. Reopen the issue with /reopen. Mark the issue as fresh by adding the comment /remove-lifecycle stale.

[dprotaso]

/unassign @Harini1023

@keshavcodex @afzal442 are you still working on this issue?

[keshavcodex]

Hey @dprotaso i wrote this, but can you tell me where should I add this file, and what should be the name of this file.

[keshavcodex]

Hey @evankanderson can you tell me where should I add this file, and what should be the name of this file.

[evankanderson]

I suspect it might make sense to put it in https://knative.dev/docs/client/ as a new file, possibly "using the CLI in automation".

[satyampsoni]

@keshavcodex are you still working on it?

[keshavcodex]

@keshavcodex are you still working on it?

No

[gouthamhusky]

/assign @gouthamhusky

[gouthamhusky]

Hi @evankanderson, this seems to a long standing open issue. To be clear, do we want to document the use of kn service create --force command > alone? I see no references to other commands like service update etc.

[github-actions[bot]]

This issue is stale because it has been open for 90 days with no activity. It will automatically close after 30 more days of inactivity. Reopen the issue with /reopen. Mark the issue as fresh by adding the comment /remove-lifecycle stale.