Skip to content
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

Infoblox provider: upgrade infoblox client to recent version #920

Closed
somaritane opened this issue Jul 11, 2022 · 4 comments
Closed

Infoblox provider: upgrade infoblox client to recent version #920

somaritane opened this issue Jul 11, 2022 · 4 comments
Labels
dependencies Pull requests that update a dependency file enhancement New feature or request
Milestone

Comments

@somaritane
Copy link
Contributor

Currently, we're using v1.1.1 version of the official Infoblox go client for the Infoblox provider.
whereas there has been a major v2.0.0 release in the client
https://github.com/infobloxopen/infoblox-go-client/releases/tag/v2.0.0
with v2.1.0 being the latest version
https://github.com/infobloxopen/infoblox-go-client/releases/tag/v2.1.0

Makes sense to analyze the possible improvements/features, and upgrade to new version if that makes sense

@somaritane somaritane added enhancement New feature or request dependencies Pull requests that update a dependency file labels Jul 11, 2022
@somaritane somaritane added this to k8gb Jul 25, 2022
@somaritane somaritane moved this to To do in k8gb Jul 25, 2022
@jkremser
Copy link
Member

jkremser commented Aug 2, 2022

It looks like the latest released version of "v2" client (which is 2.1.0), doesn't have the full support for TXT records. We need this in k8gb, because of the heart beats logic.

However, the commit has landed to the master. Are we ok with depending on non-released version? you know go get foo@abcd123 where abcd123 is the tip of the default branch. I can also create an issue on that repo that it would be nice to make a new release.

@somaritane
Copy link
Contributor Author

@jkremser I'd prefer to wait for the official v2 release.
It still makes sense to build with git sha and check if k8gb is still able to work with older Infoblox API versions.

@jkremser
Copy link
Member

jkremser commented Sep 6, 2022

I'd like to test it against a live instance of infoblox, but deploying it locally looks pretty cumbersome:

Deploying On-prem Hosts in Docker 
To deploy on-prem hosts in a Docker environment, complete the following:

In the Cloud Services Portal, go to Administration -> Downloads.

On the Downloads page, click Download Package for Docker, and then save the .tar.gz file on your system.

Set up the Docker environment on your system. Ensure that the Docker version is supported, as described in [ Deploy](https://docs.infoblox.com/space/BloxOneThreatDefense/35373572)[ ment](https://docs.infoblox.com/space/BloxOneThreatDefense/35373572)[ Requirements](https://docs.infoblox.com/space/BloxOneThreatDefense/35373572) and [ Port Usage for Bare-Metal On-Prem Hosts](https://docs.infoblox.com/space/BloxOneCloud/35398564). For information about how to install Docker, refer to the [ Docker Documentation](https://docs.docker.com/).

Download the Infoblox Docker image tar file to your server, and then execute the following command at root. Note that you must have root privileges to execute Docker commands.

# docker load -i <BloxOne_OnPrem_Docker_<VERSION>.tar.gz
...

(https://docs.infoblox.com/space/BloxOneDDI/7351312/Bare-Metal+Docker+Deployment#Deploying-On-prem-Hosts-in-Docker)

@somaritane somaritane added this to the 1.0 milestone Oct 9, 2022
@ytsarev
Copy link
Member

ytsarev commented Jul 20, 2024

Closing until actively demanded by community

@ytsarev ytsarev closed this as completed Jul 20, 2024
@github-project-automation github-project-automation bot moved this from To do to Done in k8gb Jul 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file enhancement New feature or request
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants