Skip to content

Wrong ENV_CONTROLLER_API_URL format #72

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
fabriziofiorucci opened this issue Dec 1, 2021 · 2 comments
Open

Wrong ENV_CONTROLLER_API_URL format #72

fabriziofiorucci opened this issue Dec 1, 2021 · 2 comments

Comments

@fabriziofiorucci
Copy link

fabriziofiorucci commented Dec 1, 2021

Hello, I noticed that setting in the deployment manifest:

    env:
      - name: ENV_CONTROLLER_API_URL
        value: "https://nc-apim.f5.ff.lan/1.4/"

doesn't allow the controller agent communicate with NGINX Controller, whereas:

    env:
      - name: ENV_CONTROLLER_API_URL
        value: "nc-apim.f5.ff.lan:443"

works as expected. Is this a bug or am I missing something?

Thank you,
FF

@1996sajal
Copy link
Contributor

1996sajal commented Dec 1, 2021

Hey @fabriziofiorucci,
So in agent.cong ENV_CONTROLLER_API_URL is replaced by api_url.
Here is a sample of the value in the agent.conf. So the second code snippet is correct.

[cloud]
api_url = ctrl_fqdn:443
api_timeout = 5.0
max_retention = 360

@fabriziofiorucci
Copy link
Author

@1996sajal that's correct. in the main readme, section 4.5, the variable description is:

The NGINX Controller API URL. The new instance will use the specified API URL to locate the NGINX Controller host.

I think this might be made clearer by mentioning "fqdn and port" instead of "URL".

thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants