Highlighted
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
848 views

Announcement: Beta Release of deploying Access Manager in Docker Containers

We are happy to announce the Beta release of deploying Access Manager as containers. Access Manager supports Docker for deploying the containers. Access Manager components are delivered as Docker images and are self-sufficient to run on their own.

Access Manager Docker images are optimized to run on Kubernetes, a popular container orchestration engine for Docker. Kubernetes simplifies deploying, running, scaling, and upgrading Access Manager Docker images. The Access Manager Docker images are cloud-native applications and can run in Kubernetes environments deployed on Linux servers and cloud.

The following are some of the noteworthy advantages while deploying the Docker images in Kubernetes:

  • Significantly reduced installation and upgrade time, thereby reducing the maintenance cost.
  • Decreased downtime and reduced manual intervention for upkeep. Kubernetes constantly checks the health of the Access Manager pods. If a pod stops working, Kubernetes automatically starts a new one.
  • Kubernetes offers a built-in fault-tolerant environment and therefore has no service interruption. This
  • Kubernetes has built-in isolation mechanisms such as namespaces. It allows you to group container resources using access permissions, thereby enhancing security.
  • Orchestrate and manage all container resources from a single control plane. This helps optimize the networking, load-balancing, security, and scaling across all Kubernetes nodes.
  • Access Manager components can be easily scaled up to meet high demands.
  • Support for deploying in cloud environments; Amazon EKS and Microsoft Azure AKS.
  • This release supports only a fresh installation of Access Manager v5.0. Upgrade from older versions is not supported.
  • Access Manager Docker images are supported only on a Kubernetes environment.

 

The Beta Release will be available from October 9 to December 11, 2020. As part of this program, you will get the following resources:

  • Beta build of Access Manager for your testing and feedback.
  • Early access to Documentation.
  • Dedicated forum for discussing topics related to this release.
  • Regular calls with Access Manager engineering and support teams where you can participate and share your feedback, issues, and well, kudos if we deserve it.

Looking forward to your participation.

 

DOWNLOAD LINK:

(for Helm chart)

https://dl.netiq.com/Download?buildid=43HQQphN3jU~

Labels (3)
10 Replies
Highlighted
Commodore
Commodore

Is there any other documentation on whats new ?

Highlighted
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Magnus, this Beta is specific to deploying Access Manager in Docker containers. The attached documentation talks about this support in detail. We are planning a series of Beta calls in the next few weeks to walk through the support and field any questions.

As for the upcoming NAM 5 features, we will be sharing a post soon. You might've noticed the recently released Analytics Dashboard EA as well https://community.microfocus.com/t5/Early-Access-Release-of-NetIQ/bd-p/NAMDashBeta

Gireesh 

Highlighted
Lieutenant
Lieutenant

This is great news. Will try out and provide feedback
Highlighted
Lieutenant
Lieutenant

When I deploy the helm chart on Azure AKS, I get the below error
Error: secrets "admin-credentials" already exists
It looks like the admin-credentials is defined multiple times in ac, ag and idm.
Highlighted
Micro Focus Expert
Micro Focus Expert

Can you share the command you used for the installation.

0 Likes
Highlighted
Lieutenant
Lieutenant

Please see the attached image file

 

0 Likes
Highlighted
Micro Focus Contributor
Micro Focus Contributor

By any chance was "helm install" command ran twice with/without different release name?
If so initial misconfigured data can be taken, please make sure that you uninstall the previous deployment using uninstall.sh script, clean the volume and try again. For more info on uninstall, refer uninstall section in documentation.
0 Likes
Highlighted
Lieutenant
Lieutenant

I Have uninstalled the old release and then tried also verifying the secret stores before running a fresh install.

To make sure of this, I also installed the helm chart in a completely fresh namespace. Even this came back with the same error and the failure.

0 Likes
Highlighted
Micro Focus Contributor
Micro Focus Contributor

It is kind of an unusual behavior seen here and ideally helm 3.0 should handle this. Can you provide the debug message (leaving the template) seen when helm install is run with "--debug" flag.
As a workaround for now, try deleting 'access-manager/charts/am-idp/templates/secret.yml', 'access-manager/charts/am-ag/templates/secret.yml'. Please make sure that uninstall.sh and cleaning of previous deployment's persisted data is done.
If similar error is seen on configmap, delete 'access-manager/charts/am-idp/templates/configmap.yml', 'access-manager/charts/am-ag/templates/configmap.yml'
0 Likes
Highlighted
Lieutenant
Lieutenant

Please find the output when running with --debug flag

 

bala@Azure:~/BBDTestRepo/AccessManager$ helm install second-release access-manager -n netiq --create-namespace --debug
install.go:172: [debug] Original chart version: ""
install.go:189: [debug] CHART PATH: /home/bala/BBDTestRepo/AccessManager/access-manager

client.go:108: [debug] creating 1 resource(s)
client.go:254: [debug] Starting delete for "admin-credentials" Secret
client.go:283: [debug] secrets "admin-credentials" not found
client.go:108: [debug] creating 1 resource(s)
client.go:254: [debug] Starting delete for "am-ac-volume" PersistentVolume
client.go:283: [debug] persistentvolumes "am-ac-volume" not found
client.go:108: [debug] creating 1 resource(s)
client.go:254: [debug] Starting delete for "am-config" ConfigMap
client.go:283: [debug] configmaps "am-config" not found
client.go:108: [debug] creating 1 resource(s)
client.go:254: [debug] Starting delete for "am-edir-initialization" PersistentVolume
client.go:283: [debug] persistentvolumes "am-edir-initialization" not found
client.go:108: [debug] creating 1 resource(s)
client.go:254: [debug] Starting delete for "am-edir-volume" PersistentVolume
client.go:283: [debug] persistentvolumes "am-edir-volume" not found
client.go:108: [debug] creating 1 resource(s)
client.go:108: [debug] creating 9 resource(s)
Error: secrets "admin-credentials" already exists
helm.go:94: [debug] secrets "admin-credentials" already exists

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.