K8s templates have wrong image references

[bhardwahnitish19]

fabric-deployment-register-peer.yaml and fabric-deployment-register-orderer.yaml are referring to CA's image to spin up peer and orderer containers respectively.

For an instance:

apiVersion: apps/v1
kind: Deployment
metadata:
namespace: %DOMAIN%
name: register-p-%ORG%
spec:
replicas: 1
strategy: {}
selector:
matchLabels:
app: hyperledger
role: peer
org: %ORG%
name: register-p-%ORG%
template:
metadata:
labels:
app: hyperledger
role: peer
org: %ORG%
name: register-p-%ORG%
spec:
containers:
- name: register-p-%ORG%
image: hyperledger/fabric-ca:%FABRIC_TAG%
env:
- name: PEERORG
value: %ORG%
command: ["sh"]
args: ["-c", "/scripts/register-peer.sh 2>&1; while true; do sleep 90; done;"]
volumeMounts:
- mountPath: /scripts
name: rca-scripts
- mountPath: /data
name: rca-data
volumes:
- name: rca-scripts
persistentVolumeClaim:
claimName: rca-scripts-%ORG%-pvc
- name: rca-data
persistentVolumeClaim:
claimName: rca-data-%ORG%-pvc

[msolefonte]

It seems to be your problem. If you check the peer YAMLs [1] and [2], you can can see that the image used is the correct one: image: hyperledger/fabric-peer:%FABRIC_TAG%. Same things happens with the orderer YAMLs [1], [2] and [3]. You can see there that image: hyperledger/fabric-orderer:%FABRIC_TAG% is being used.

UPDATE: I have just seen the problem. You are not looking the peer and orderer deployments but the register deployments, which have to be a fabric-ca image.