Skip to content

Conversation

@ivankatliarchuk
Copy link
Member

@ivankatliarchuk ivankatliarchuk commented Jan 1, 2026

What does it do ?

Remove cloudfoundry support

It was added in 2018 #955

No documentation, no updates since 2018. I was using Cloudfoundry years back. Not sure what exactly this code should support. Basically cloudfoundry does not require external-dns, and is a different platform.

Most recent cloudfoundry is very much integrated with Kubernetes https://www.cloudfoundry.org/technology/korifi/, and it does support ingress, service and etc, so does not require anything specific.

Motivation

More

  • Yes, this PR title follows Conventional Commits
  • Yes, I added unit tests
  • Yes, I updated end user documentation accordingly

@k8s-ci-robot k8s-ci-robot requested a review from vflaux January 1, 2026 13:30
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 1, 2026
@ivankatliarchuk ivankatliarchuk force-pushed the chore-remove-cloudfoundry-source branch from e3113a0 to 16f05cd Compare January 1, 2026 13:37
@coveralls
Copy link

coveralls commented Jan 1, 2026

Pull Request Test Coverage Report for Build 20764473363

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 115 unchanged lines in 2 files lost coverage.
  • Overall coverage increased (+0.08%) to 78.898%

Files with Coverage Reduction New Missed Lines %
apis/externaldns/types.go 1 99.62%
store.go 114 43.01%
Totals Coverage Status
Change from base Build 20762676915: 0.08%
Covered Lines: 15894
Relevant Lines: 20145

💛 - Coveralls

"context"
"net/url"

cfclient "github.com/cloudfoundry-community/go-cfclient"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤔 Shouldn't we remove this go-cfclient then?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

Copy link
Collaborator

@mloiseleur mloiseleur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cloudfoundry should then also be removed in flags and docs, or did I miss something?

@ivankatliarchuk ivankatliarchuk changed the title chore(source): remove cloudfoundry support chore(source)!: remove cloudfoundry support Jan 3, 2026
@k8s-ci-robot k8s-ci-robot added apis Issues or PRs related to API change docs labels Jan 3, 2026
@ivankatliarchuk
Copy link
Member Author

Correct. Removed

@vflaux
Copy link
Contributor

vflaux commented Jan 3, 2026

There is still some refs to cloudfoundry:

  • func TestParseFlagsCloudFoundry(t *testing.T) {
    t.Parallel()
    cfg := parseCfg(t,
    "--cf-api-endpoint=https://api.cf.example",
    "--cf-username=user1",
    "--cf-password=p@ss",
    )
    assert.Equal(t, "https://api.cf.example", cfg.CFAPIEndpoint)
    assert.Equal(t, "user1", cfg.CFUsername)
    assert.Equal(t, "p@ss", cfg.CFPassword)
    }
  • // - CloudFoundryClient: CloudFoundry platform client
  • // - "cloudfoundry": CloudFoundry applications
  • Cloudfoundry Type = "cloudfoundry"
  • | `--cf-api-endpoint=""` | The fully-qualified domain name of the cloud foundry instance you are targeting |
    | `--cf-username=""` | The username to log into the cloud foundry API |
    | `--cf-password=""` | The password to log into the cloud foundry API |
  • // Flags related to cloud foundry
    b.StringVar("cf-api-endpoint", "The fully-qualified domain name of the cloud foundry instance you are targeting", defaultConfig.CFAPIEndpoint, &cfg.CFAPIEndpoint)
    b.StringVar("cf-username", "The username to log into the cloud foundry API", defaultConfig.CFUsername, &cfg.CFUsername)
    b.StringVar("cf-password", "The password to log into the cloud foundry API", defaultConfig.CFPassword, &cfg.CFPassword)
  • CFAPIEndpoint string
    CFUsername string
    CFPassword string
  • CFAPIEndpoint string
    CFUsername string
    CFPassword string

@ivankatliarchuk
Copy link
Member Author

Removed as well

Copy link
Contributor

@vflaux vflaux left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 5, 2026
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 6, 2026
@mloiseleur
Copy link
Collaborator

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 7, 2026
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mloiseleur

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 7, 2026
@k8s-ci-robot k8s-ci-robot merged commit d2fb11a into kubernetes-sigs:master Jan 7, 2026
18 checks passed
@ivankatliarchuk ivankatliarchuk deleted the chore-remove-cloudfoundry-source branch January 7, 2026 08:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

apis Issues or PRs related to API change approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. docs lgtm "Looks good to me", indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. source

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants