What's new in Version 10.0.1.8-eus

Version 10.0.1.8-eus ifixes

10.0.1.8-ifix1-eus

Version 10.0.1.8-ifix1-eus contains only fixes.

What's new for Developers

API's policy version must match the gateway's policy version

API Connect will only publish an API to the gateway if the policy version in the API's assembly exactly matches the version that is present on the gateway.

This is a change from the behavior in earlier releases of API Connect, which published the API if its policy version was considered to be compatible with the gateway's version. In that scenario, the published API would fail at the gateway due to the version difference. The new behavior mitigates the problem by requiring the API to use the correct version of the policy.

What's new for Developer Portal administrators

New commands are available in the Developer Portal command-line tool

The following commands for managing forums are now available in the Developer Portal command-line tool:

• forums:disable - Deletes any existing forums taxonomy terms, and then disables the Forum module for a given site.
• forums:enable - Enables the Forum module for a given site.

For more information, see Using the forums commands.

What's new for DevOps

Ability to disable the Portal web endpoint check

When you create or register a Developer Portal service, the Portal subsystem checks that the Portal web endpoint is accessible. However sometimes, for example due to the complexity of public and private networks, the endpoint cannot be reached. In this instance, you can disable the Portal web endpoint check so that the Developer Portal service can be created successfully.

To disable the endpoint check, complete one of the following updates depending on your platform:

On Kubernetes, OpenShift, and IBM Cloud Pak for Integration

Add the following section to the Portal custom resource (CR) template:

spec:
  template:
  - containers:
    - env:
      - name: PORTAL_SKIP_WEB_ENDPOINT_VALIDATION
        value: "true"
      name: admin
    name: www

On VMware

In your apicup project, create a file called ptl-extra-values.yaml (or edit the file if one already exists), and add the following section:

spec:
  template:
  - containers:
    - env:
      - name: PORTAL_SKIP_WEB_ENDPOINT_VALIDATION
        value: "true"
      name: admin
    name: www

For more information, see Registering a Portal service.

Ability to specify Kubernetes ingress class

When installing on Kubernetes you can specify an alternative ingressClassName, instead of the default nginx ingress class. See Installing the Management subsystem cluster.

API Connect 10.0.1.8-eus uses a new version of cert-manager

• Kubernetes, VMware: cert-manager 1.7.1

  When you refer to cert-manager in your CRs or commands, the following values must be updated to reflect the newer version of cert-manager: In VMware, references to cert-manager in CRs are updated during the upgrade.

  • cert-manager-0.10.1.yaml becomes: cert-manager-1.7.1.yaml
  • ingress-issuer-v1-alpha1.yaml becomes: ingress-issuer-v1.yaml
  • certmanager.k8s.io becomes: cert-manager.io
• OpenShift, Cloud Pak for Integration: cert-manager 3.21 (provided by Foundational Services)
  When you refer to cert-manager in your CRs or commands, the following values must be updated to reflect the newer version of cert-manager:

  • cert-manager-0.10.1.yaml becomes: cert-manager-3.21.yaml
  • ingress-issuer-v1-alpha1.yaml becomes: ingress-issuer-v1.yaml
  • certmanager.k8s.io becomes: cert-manager.io

APICOPS command to detect stale certificates

The new apicops command apicops upgrade:stale-certs returns a list of stale certificates; for example, so that you can delete them after a certificate manager upgrade. The API Connect upgrade instructions now include a step explaining when and how to check for stale certificates. For information on the apicops tool, see The API Connect operations tool: apicops.