# Redefining the CCM name without using another CCM

**URL:** <https://forums.suse.com/t/redefining-the-ccm-name-without-using-another-ccm/42259>\
**Category:** k3s, k3OS, and k3d\
**Created:** [December 30, 2023, 11:11am UTC](https://forums.suse.com/t/redefining-the-ccm-name-without-using-another-ccm/42259 "2023-12-30T11:11:28Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![provamo](https://avatars.discourse-cdn.com/v4/letter/p/ee59a6/32.png) [@provamo](https://forums.suse.com/u/provamo)\
**Post date:** [December 30, 2023, 11:11am UTC](https://forums.suse.com/t/redefining-the-ccm-name-without-using-another-ccm/42259/1 "2023-12-30T11:11:28Z")

</div>

Some services I use require instances to have a specific name that starts with ‘gce://’.  
I got it to work using `--kubelet-arg=provider-id=...` without using the `--disable-cloud-controller` option.  
Could this cause internal problems in a K3S cluster?

Many thanks