Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 09-08-2018 10:58 AM
Hi,
I'm using Cloudbreak 2.7.1 and I'm in a locked down environment with proxy set up.
I was able to configure everything properly, cbd can talk to my cluster and the basic cluster was deployed successfully.
However, that's not the case when I enable Knox Gateway on a cloudbreak level. The whole installation fails.
I think it's a bug (knox is not ambari managed, so I guess it's installed in different way and it doesnt respect proxy env vars or similar) , which I don't know how to resolve.
This is currently a blocker for me.
Created 09-11-2018 09:12 AM
Hi @Jakub Igla,
Could you install a cluster without CB managed Knox and add Knox service via Ambari? If it solves your problem I suggest you should use Knox gateway this way.
Created 09-11-2018 09:12 AM
Hi @Jakub Igla,
Could you install a cluster without CB managed Knox and add Knox service via Ambari? If it solves your problem I suggest you should use Knox gateway this way.
Created 09-17-2018 02:21 PM
Hi @mmolnar
I've deployed Knox via Ambari and it works as expected. Now I have Cloudbreak and the cluster 100% behind the proxy.